ollydbg23's profile - activity

BTW, in year 2015, I have released a python script which can show the image in a separate thread of the GDB, which don't

Hi, I haven't got any email notification about your replies in year 2017, and I see your post now in year 2019. Many tha

void cvSetModeWindow_W32( const char* name, double prop_value)

This function is in opencv246\modules\highgui\src\window_w32.cpp There are some code like:

if (window->status==CV_WINDOW_NORMAL && prop_value==CV_WINDOW_FULLSCREEN)

Is this correct? compare with a double value???

The problem is solved, see: Visualize in memory OpenCV image or matrix from GDB pretty printers

Hi, thanks for the comments, I read both of them. I think my contribution will not be a git merge request, nor a Youtube video showcase. But refer from the links above, the remaining types of contribution need to send emails to [email protected], which I have did already, but with no response yet. I can't find a better way.

Hi, about months ago, I wrote emails to [email protected], but it has no response. I have write to this email list before, but that still get no response, the mail list is dead? Any links to the mail list achieves?

Back to my question: I have create a GDB python script to let me show a in memory cv::Mat window while debugging under GDB, this is much like Image Debugger Plug-in for Visual Studio, but it is for GDB.

I post this to GDB mail-list already. So, you can see the post in GDB mail-list achieve here (Visualize in memory OpenCV image or matrix from GDB pretty printers, I hope I can find a way to announce to OpenCV community. Thanks.

PS: this is the way to solve a question asked by myself: GDB pretty printer for showing iplImage or cv::Mat?

Hi, I'm considering a GDB pretty printer to show a IplImage or cv::Mat in a window when I'm debugging a C/C++ program, I Googled and find only one: https://github.com/renatoGarcia/gdb-imshow

I have GDB(python enabled, PIL library installed, WinXP), but I get "_imaging C module error in python PIL" error if I try to run the command "cv_imshow img" which img is a cv::Mat or IplImage * under GDB.

Anyone has encounter the same issue?

BTW: I have tried the way said in http://effbot.org/zone/pil-imaging-not-installed.htm , command "import _imaging" runs correctly. So, it looks like my issue is only happens under GDB command line.

Edit: I see the OpenCV official release already contains a python binding, E.g. In OpenCV 2.4.4, there is a file: OpenCV-2.4.4.exe\opencv\build\python\2.7\cv2.pyd. Can I use this python interface to show an IplImage when I'm debugging an C/C++ OpenCV application?

Hi, Alexander Shishkov, thank you for the answer. (though my reply is a bit late, but still thanks for the clarification) Now, I see there are 2.4.4 opencv release. So do they use the same mingw compiler suite as 2.4.3? I mean: For x64, you use mingw-w64 gcc 4.6.3 ( I guess dw2 version, but I haven't tried) For x86, you use mingw from official mingw site, gcc 4.6.1 dw2 version.

Am I right?

Btw: I strongly suggest that you need to tell the user what the gcc suite to build those prebuild libraries. I think those information should be put in a text like "readme.txt" Thanks.

Hi, I found that the OpenCV-2.4.3.exe file is quite huge, if I unzip it, it will takes larger then 3G Bytes. So, I just extract the pre-build libs for mingw (x86) and the include folder.

Now, here comes a question: I use the dependency walkers to check the files under: OpenCV-2.4.3.exe\opencv\build\x86\mingw\bin\, it looks like those dlls was depend on some dlls like: LIBGCC_S_DW2-1.DLL and LIBSTDC++-6.DLL. So, where does those dlls come from. I mean: which mingw compiler suite was used to build the mingw libs.

Currently, there are a lot of mingw suites in the world, TDM-GCC 4.6.x? official-mingw 4.6.x or official-mingw-4.7.x? Some compilers were DW2 and others were SJLJ exception module.

I can't find any documents about this, thanks.(also, I would like to see the build log(options passed to the gcc)

Here is my test app code:

#include <stdio.h>
#include "opencv2/core/core.hpp"
#include "opencv2/imgproc/types_c.h"

using namespace cv;

int main()
{
    printf("Hello world!\n");
    Mat x = Mat(4, 4, CV_32S);

    return 0;
}

Also, the bt of the crash:

    Program received signal SIGSEGV, Segmentation fault.
In libstdc++-6!_ZN9__gnu_cxx18__exchange_and_addEPVii () (E:\code\gcc\MinGW\bin\libstdc++-6.dll)

[debug]> bt 30
[debug]#0  0x6fc5b94e in libstdc++-6!_ZN9__gnu_cxx18__exchange_and_addEPVii () from E:\code\gcc\MinGW\bin\libstdc++-6.dll
[debug]#1  0x6fc58bbc in libstdc++-6!_ZN9__gnu_cxx12__atomic_addEPVii () from E:\code\gcc\MinGW\bin\libstdc++-6.dll
[debug]#2  0x6fc60c76 in libstdc++-6!_ZN9__gnu_cxx9free_list8_M_clearEv () from E:\code\gcc\MinGW\bin\libstdc++-6.dll
[debug]#3  0x6fc89d6e in libstdc++-6!_ZNSs4_Rep10_M_refcopyEv () from E:\code\gcc\MinGW\bin\libstdc++-6.dll
[debug]#4  0x6fc89e66 in libstdc++-6!_ZNSs4_Rep7_M_grabERKSaIcES2_ () from E:\code\gcc\MinGW\bin\libstdc++-6.dll
[debug]#5  0x6fc8bf4b in libstdc++-6!_ZNSsC1ERKSs () from E:\code\gcc\MinGW\bin\libstdc++-6.dll
[debug]#6  0x61bf773e in _fu2730___ZNSs4_Rep20_S_empty_rep_storageE () from E:\code\opencv\2.4.3\mingw\bin\libopencv_core243.dll
[debug]#7  0x61bbe1cc in _fu1594___ZNSs4_Rep20_S_empty_rep_storageE () from E:\code\opencv\2.4.3\mingw\bin\libopencv_core243.dll
[debug]#8  0x0022fea0 in ?? ()
[debug]#9  0xffffffff in ?? ()
[debug]#10 0x00000000 in ?? ()
[debug]>>>>>>cb_gdb:
[debug]> quit