Visual D debugging messed up

[Rainer Schuetze]

On 02/05/2018 21:56, IntegratedDimensions wrote:
> Lots of temp variables and breakpoints are not hit: says missing symbols 
> but then next line works fine. Sometimes the stack trace doesn't work, 
> sometimes it does. Won't break sometimes if the BP is the last line of a 
> block. Everything latest version and fresh install and in x86 mode.

To hide the temporaries go to Tools->Options->Debugging->Mago and enable 
"Hide compiler generated symbols".

If you are using VS2013 or later, I'd recommend selecting the "Visual 
Studio" debug engine, as this has the mago D expression evaluator 
plugged into the native VS debugger for better integration.

For stacktraces, you can sometimes end up in a system call where the 
debugger doesn't know how to walk the stack. Usually loading the symbols 
from the Microsoft symbol server helps here.

If there is some strange things happening regarding breakpoint 
positions, that's likely inaccurate debug information emitted by the 
compiler. It would be good if you could isolate examples and post them 
to bugzilla: https://issues.dlang.org/