Hey I'm writing a small tool to do mem leak check, and later GDI leak checks. That tool, named 'examine', is intended to be used like valgrind, that is, no linkage (unlike mpatrol, for example). The usage is : examine my_test_app.exe
I've beginning to write it for several reasons. First : improving mpatrol, but the lead dev, Graeme Roy is busy for several months. Secondly, by curiosity (how to do such things). And finally, to use it in one of the projects i'm involved in (the Enlightenment project), until mpatrol supports that feature (no linkage of the app against mpatrol library). The desing is : DLL injection, API hooking and stack trace (using libbfd). The overloading of the memory functions seems correct (though there is a small little bug), but the stack tracing seems broken. While it works with my test examples, when I use it with 'examine', the call stack seems to "be" only in the DLL. More precisely, instead of having something like: my_app.c : line 18 my_app.c : line 56 crtexe.c : line ??? crtexe.c : line ??? I only get : crtexe.c : line ??? crtexe.c : line ??? I've searched a lot but i can't find anything. The code can be downloaded in our svn repo : svn co http://svn.enlightenment.org/svn/e/trunk/DEBUG/examine or can be viewed here : http://trac.enlightenment.org/e/browser/trunk/DEBUG/examine/src/lib http://trac.enlightenment.org/e/browser/trunk/DEBUG/examine/src/bin Any help or ideas are greatly appreciated thank you regards Vincent Torri ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
