[Windows & DMD] No callstack when crash with Access violation reading location 0x00000000

[Xavier Bigand]

Le 11/01/2014 19:40, Benjamin Thaut a écrit :
> Am 11.01.2014 19:16, schrieb Xavier Bigand:
>> Le 11/01/2014 18:45, Benjamin Thaut a écrit :
>>> Am 11.01.2014 17:24, schrieb Xavier Bigand:
>>>> I get some troubles to solve a memory bug, just cause I don't have any
>>>> informations for debuggers and I can't neither use DrMemory.
>>>>
>>>> Is it possible to get the callstack when calling a method on a null
>>>> pointer with specifics DMD flags?
>>>>
>>>> Maybe DMD need add null ptr call checks in debug mode?
>>>
>>> For x64 exeuctables compile with -g.
>>> For x86 executables compile with -g and then run cv2pdb on the final
>>> executable. cv2pdb is part of VisualD.
>>>
>>> Kind Regards
>>> Benjamin Thaut
>>
>> Yep I am using VisualD with cv2pdb, and I build in debug mode with the
>> flag -g.
>>
>
> And it does not print a stack trace? Is it possbile that this access
> violation happens within a module constructor?
>
> Try importing core.sys.windows.stacktrace into every single one of your
> modules and see if that changes something.
>
> Kind Regards
> Benjamin Thaut

Yes I have no stack trace and adding import core.sys.windows.stacktrace 
change nothing.