Geek Answers Handbook

Extract debug information from msys / mingw gcc dll using rebase.exe?

I am trying to analyze a mini crash dump and need symbol files to get more details about the crash. Im currently just seeing: "034eff74 0086eee9 00000000 0089d58d 034eff94 app_integrator! ZNK14ACE_Data_Block4baseEv + 0x6"

Is it possible to extract debugging information from the built-in msys / mingw gcc dll into a readable Windbg format? If not, is there another way to get more detailed information, such as how to download a MAP file?

DLLs and all contained .o files are created with the -g flag.

+6
debugging dll msys mingw windbg
source share
1 answer

Windbg cannot handle the debugging information that will be generated with -g when installing mingw. However, it can supposedly deal with COFF characters.

If the source files for your DLL are small enough, you can get COFF debugging information for the build (-gcoff, not -g).

So, Windbg can (supposedly) handle COFF characters, and GCC can generate them. So it should be easy from there, right? I tried to do just that with a Win32 executable file created by Visual Studio 2008 that loaded a gcc-compiled DLL. Unfortunately for me compilation with -gcoff did not work. Mingw gcc will not generate COFF characters for projects with more than 64k lines of code. The DLL I used was significantly larger than 64K lines of code. Unfortunately, I have to admit, I gave up and stepped back on the correct OutputDebugString. Otherwise, I can give more complete instructions. I did not want to explore the possibility of creating gcc do COFF characters for large source files or an alternative way to write debugging extensions to parse DWARF or STABS data in windbg internal symbol tables.

I fixed the problem by the way!

Further suggestions can be found in this forum at windbg.info .

+5
source share

More articles:


All Articles