Re: [Mingw-users] Memory Debugging Tools for MinGW

[Luke D. <cod...@ho...>]

----- Original Message ----- 
From: "David Eisner" <cr...@um...>
To: <min...@li...>
Sent: Friday, July 25, 2003 12:08 AM
Subject: Re: [Mingw-users] Memory Debugging Tools for MinGW


>
> That worked (using the snapshot).  Thanks!  Now Purify
> can instrument the executable and it reports the error.
>
> The next problem is that Purify is unable to locate the error
> in the source code, as it does with the MS compiled executable.
>
> I compiled with -g, but I don't think Purify understands the debugging
> data generated by MinGW.  According to the Purify docs, it wants
> either .pdb files, .dbg files, .map file, or "embedded in a
> module" -- but I'm not sure what format.
>
> Am I SOL, or is there some way to get MinGW to generate debugging
> data in a format Purify can understand?
>
> Thanks again for all your help.
>
> -David

I doubt that it it is possible to get line numbers. The GNU linker can
generate map files (-Wl,-Map,filename.map) but they don't look like MSVC
ones, and anyway it would only tell you the function names, not the line
numbers. In case you didn't know, you can manually look up a line number for
a code address with the addr2line command:

addr2line -e hello.exe 0x00401234

Luke