Attila Kovacs

I'd write them in the meantime, they should work too 😛

Agree for recurring tasks. I think a listview on a dockform and a code navigaion routine is not that hard.

How would you click on a line which can't be evaluated with the built in search? 🙂

There are many linux tools for windows or there is the linux subsystem for windows, or even powershell if you are masochist, why would you use the very limited IDE search?

AMD uProf failed every time I tried so I'm not wondering. Their forum is also full of complaints about that.

Yes, OllyDbg, as I wrote before. Works like a dream. So basically every debugger which supports pdb will work.

Try with one field at the time. <o>

you could read those offsets from the PE (optionally), you are already iterating through the sections, should not be a big problem

Just tested with a D2007 project and no problems at all.

I've seen in procmon that something happens but slow af and had nothing to do with the pdb. I'm still waiting for the confirmation email for the intel tech forum where google found some similar posts.

My VTunes stucks here:

There is however this message on bind: "Image does not contain a debug directory address - please link with debug info enabled" It's enabled. edit: hmmmm .debug is not present in the exe edit2: got it, place debug info in a separate tds file was checked

Well, OllyDbg loads fine a 27Mb pdb and I picked an address from the end of the map and it's translated in the debugger. Great work!

yep: Debug info formats: ▪ PDB, COFF, DWARF, STABS

yes yes yes yes yes yes yes! finally we can debug too! @Anders Melander it works! \o/