David Heffernan David Heffernan k 36 36 gold badges silver badges bronze badges. So if anyone can get the specs for it?! Just for your information: These versions are available in this archive: The pdb creation threw up huge numbers of errors.
|Date Added:||22 August 2012|
|File Size:||56.89 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Here’s a compiled version of the latest sources of cv2pdb. Sign up using Facebook.
Subscribe to RSS
Email Required, but never shown. Should I even expect map2dbg to work in 64 bit? Alex Whiter Alex Whiter 1 1 silver badge 4 4 bronze badges. Unfortunately, non-default calling conventions do not improve the stack frame info. So it probably won’t work, but you can try it anyway David Heffernan k 36 36 gold badges silver badges bronze badges. ProcesExplorer runs only in 64bit in a 64bit Windows, but ProcesHacker also has a 32bit version.
Here is the archive: It does indeed produce. When I have some more time I can maybe improve it further It is some kind of proxy dll: Asked 7 years, 7 months ago.
Google Code Archive – Long-term storage for Google Code Project Hosting.
I think the reason why we cannot see the correct stack info is Delphi uses some not standard stack frames as compared to MS VC.
That’s maap2dbg I created my own stack viewer and minidump viewer, which uses Delphi debug symbols. I hope it can modified to read Delphi. For 64 bit executables the call mao2dbg map2dbg. Sign up using Email and Password. Unicorn Meta Zoo 9: I found a PDB writer https: They have symbols from my executable, but they are clearly not the right symbols.
So even if it creates a valid. David Heffernan David Heffernan k 36 36 gold badges silver badges bronze badges. Can I use map2dbg with 64 bit Delphi executables?
map2dbg download, free map2dbg download.
Improving the question-asking experience. XE and certainly XE2 are not mentioned. I have tried several things, but no success yet.
I guess you’re right – sorry to get your hopes up.
I’ve tested a couple of DBGs in WinDbg, and the symbols were correctly assigned with their addresses.
I don’t think so. I’ve modified the project from codeproject. I had a go with this but it looks like it needs a lot more polish. When I view stack traces in Process Explorer, map2ddbg have no symbol names.