Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: David Lamy-Charrier <david.lamy@gm...> - 2005-12-07 09:32:59
I am using trying to debug the following system on a Win XP Pro PC:
A prog.exe compiled with MSVC6.0 in release mode, load a mod1.dll
compiled with MSVC6.0 in release mode, which then loads a mod2.dll
compiled with GCC with debugging information.
( I am developping a kind a plug-in dll for an application and I don't
have the source code of this application).
To debug in my dll (mod2.dll), I add an "asm("int $3");" in the source
code, then I run the prog.exe in insight and when the "int 3" is
reached I can easily steps and debug in my dll.
But if use gdb 6.3 + insight 6.1 (posted on Sept 24, 2005), the Call
Stack seems completely wrong and incredibly deep, (I know that the
stack frame is a very central and complex problem in GDB...).
If I use latest gdb + insight (posted on Nov 17, 2005), the Call Stack
looks better with a reasonable depth but it failed to load the debug
information of my dlls apparently because there are space in the path
So, it seems the latest version corrects the problem to decode the
call stack (cool !!) but
there is a regression on the support of space in path names !!
Does anybody already encounter this problem ?
Could you give me any hints to find the appropriate source file I
should look at to correct the space in pathname problem with latest
Thanks in advance,