Had another 48hr game jam this weekend...

[Paolo Invernizzi]

On Monday, 2 September 2013 at 00:15:28 UTC, H. S. Teoh wrote:
> But I will say that debugging can and must be improved. 
> Currently, about
> the only thing usable for dmd -g is to get a stacktrace of a 
> program
> crash. Nothing else seems to be properly supported (I use gdb). 
> Stepping
> through statements and setting breakpoints more-or-less works, 
> but I
> can't get at most variables (keeps complains about being unable 
> to
> reference 'this' or something similar), sometimes variable 
> values are
> outright wrong or completely unrelated to the actual value, 
> sometimes
> variables shown right on the source line being debugged don't 
> exist in
> the debugger ('no such symbol'). Unable to look into nested 
> structs
> without hitting odd behaviour. Doesn't understand D naming 
> conventions
> (or does so poorly).
>
> Basically, I've given up trying to use gdb on D programs except 
> when I
> need to find out where a crash is happening. Using writeln 
> debugging is
> far more productive, sadly to say. I can imagine this state of 
> affairs
> is quite disappointing to many potential D adopters.
>
>
> T

I *strongly* agree.

- Paolo