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-12 11:38:03
I have a windows executable compiled with MSVC6.0 in release mode
which loads a dll compiled with GCC 3.4.4 minGW with debug info.
When I put a breakpoint in my DLL, I am able to step in it at assembly
and C source level,
but the call stack ( "bt" command in gdb is completely wrong).
I tried with :
- gdb6.3.1, the call stack appears with a depth of 2078 frames but it
is completely false with a lot of 0x0000000 in it and some strange
- gdb6.3.2, (from November28, 2005, available n download area, but
never announced)I get the same results, comparing the source code of
gdb6.3.1 and gdb6.3.2, it looks really similar except warning filters
- insight-6.3.50-20051116-cvs, the call stack now contains only 20
entries, but it is still wrong.
Furtermore, this release behaves differently between Windows XP
Service Pack 1 and Windows XP Service Pack 2.
--> This version also contains a bug in win32-nat.c in
register_loaded_dll() function, the field so->so_name is not
initialized before calling solib_symbols_add() causing this function
to always fails.
Is Stack unwinding between MSVC6.0 and GCC supposed to work correctly?
Does anybody also encounter the above bug with
insight-6.3.50-20051116-cvs version ?