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

[David E. <cr...@um...>]

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


On Thu, 24 Jul 2003, Luke Dunstan wrote:

> The MinGW linker generates a ".reloc" section if either you are building a
> DLL (-shared) or if your .exe has exported functions. Ideally I guess an
> equivalent option for "/fixed:no" should be added, but a workaround would be
> to add a dummy exported symbol somewhere in the source:
>
> int __declspec(dllexport) dummy;
>
> However, I believe this feature was added fairly recently so you might need
> to use the 2.14.90 snapshot of binutils.
>
> Luke
>