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/

great! thank you. I'll test is right now. the 16Mb+ is "just" some recursive stuff, looking forward to it!

It's true, that's why I tried to read all kind of pdb's with it to see if it fails on them but could not find any.

@Anders Melander 8mb/14mb I can send you if you want. Jetbrains dotPeek says that it can not read beyond the stream. Also, offset size / files count mismatch. The latter is at the end of the file right before the filenames, ~3rd field in the table.

@Anders Melander this tool works on the pdb of the test app but does not show anything on a bigger project https://github.com/Microsoft/microsoft-pdb/blob/master/cvdump/cvdump.exe there is somewhere just a tiny glitch I'm sure

As for the lines, if they are empty (xxx:00000000) there is either no code in the unit or the unit was in the project but not used anywhere, thus it's not linked to the exe. At least these are my observations. Sadly still no luck with a bigger project. OllyDbg loads the pdb without yielding any error, but can't really use it. Same in VTunes, obviously.

@Anders Melander did you update the exe? can I try it?

@Anders Melander hohooo!!! The test project's pdb just works fine with OllyDbg!!! Is that cool! I'd contribute with pleasure to get that right with large projects too but I can't deal with inline vars.

me neither, everything func@addr there must be something with the pdb as I can't even use it in a debugger, I'll try with simpler ones

okay, my first try was 26Mb pdb. Where is the problem with larges sizes as 16Mb? [58555] Failed to resolve symbol to module: 0005:00000098 SysInit.TlsLast [58557] Failed to resolve symbol to module: 0004:FE72B000 SysInit.__ImageBase Is that bad? exe was not patched, not sure if because of the messages above or because of the 26Mb limit, no real information. edit: ok, tested with another project, same messages, deleted the lines from the map, exe was patched fine with pure -bind and exe was not ptached with -bind:filename.exe

Depending on the MTA settings it could keep and try to pass it to the MX for even 5+ days. Date could also be in the future and not only in the past. Spamfilters are ranking emails with points, you could adopt this method. Also, you could look up spamassassin's and policyd-weight's rules to find out more.