How to get stack trace on Windows?

Dmitry Olshansky dmitry.olsh at gmail.com
Fri Jul 22 04:58:43 PDT 2011


On 22.07.2011 15:02, Nick Sabalausky wrote:
> "Dmitry Olshansky"<dmitry.olsh at gmail.com>  wrote in message
> news:j0bgt7$176q$1 at digitalmars.com...
>> On 22.07.2011 6:54, Nick Sabalausky wrote:
>>> I'm not getting any of the function names on the stack traces.
>>>
>>> I tried everything I found in here:
>>> http://www.digitalmars.com/d/archives/digitalmars/D/Windows_Stack_Traces_Function_Names_136887.html
>>>
>>> - I installed the "Debugging Tools for Windows" to update my dbghelp.dll
>>>
>>> - I'm already compiling/linking in one step, and using -g (also
>>> tried -gc)
>>>
>>> - I tried running the executable through cv2pdb.
>>>
>>> None of it's working.
>>>
>>>
>> Last time I've seen stack trace it was due to this command:
>>
>> dmd -debug -g ...
>>
> I was already using -debug and -g. No function names.
>
Now that's wierd, since I definitely see them. Another thing to try is 
rebuild dmd/druntime/phobos from latest git, at least it's a setup I 
have right now it works (though I'm on Win7 x64).

BTW I haven't touched dbghelp in anyway(at least any that I know of) but 
I have something like 6 versions of them on harddrive, most "public" ones:
834Kb in C:\Windows\SysWOW64  ( this one should load for 32bit apps I think)
1.03Mb in C:\Windows\System32  (64bit obviously)

for others, I'll list only sizes:
747Kb
0.99Mb
1.27Mb
1.30Mb

-- 
Dmitry Olshansky



More information about the Digitalmars-d-learn mailing list