On Jan 16, 2008 12:25 PM, Eric Pouech <[EMAIL PROTECTED]> wrote: > the hard part is not about understanding the .pdb format > our winedump already does it !! > and dbghelp supports coff and .pdb debug information (less tested than > stabs and dwarf2 of course)
That's good to hear. I must have blinked :-) > the hard part is to tell valgrind about information about modules it > doesn't know of: > - it doesn't know about the loading of the module (it's seen by vg as a > simple mmap) > - it doesn't know about the PE native debug information (whatever it is) > > the simplest approach would be to somehow: > - use the --db-attach option in vg to hook to a debugger on every error > (one hurdle is that valgrind doesn't allow both trace-children and > db-attach) > - then use winedbg to get a backtrace (or similar info) from the running > program (winedbg will be able to get to both .pdb and dwarf debug info) > > the ultimate goal is rather to ask vg to support new messages about: > - loading / unloading modules > - having external .so files to understand more detailed information, and > implement in them pdb and coff support Thanks for the tips. I don't suppose you'd have time to look at any of this? :-) - Dan