End user experience with D

[Paolo Invernizzi]

On Sunday, 1 September 2013 at 23:22:30 UTC, Adam D. Ruppe wrote:
> On Sunday, 1 September 2013 at 22:21:10 UTC, Ramon wrote:
>> Finally and possibly most importantly, basically not having 
>> fully working  debugger support is a very serious lack.
>
> Maybe it is because I write 100% bug free code the first time 
> every time ( :-) ) but I've found the gdb support, at least on 
> Linux, to be really pretty good.
>
> I compile with -gc -debug - the "pretend to be C" option is 
> something I started doing years ago and might not be necessary 
> anymore, but I've found it to be plenty good enough anyway.
>
>> D's bias toward Windows doesn't help either.
>
> If anything, I don't think D goes far enough in its Windows 
> support. It works well there, sure, even the optlink things 
> others complain about don't bother me, but there's a lot of 
> stuff it could easily do and doesn't, at least not without 
> grabbing additional downloads.
>
> On Linux, dmd works quite excellently, as do gdc and ldc.

Adam,

Me and my colleague are working full time for a project with DMD 
2.063: I'm on OSX, so it's a different story, but he is on linux 
(Ubuntu 13.04 64bit).

He is VERY interested in being able to use the debugger, first of 
all from command line (just to understand at first glance what is 
working and what not...).

I've read a lot of thread about debugging, mainly related to 
stack-trace or sigfault, but what we are rely missing is the 
ability to set a break (usually that's work, at least in OSX), 
AND being able to inspect locals.

I think we are not alone searching for such informations, so can 
you point me somewhere in the wiki, in the documentation, or 
similar, when there's a clear information about what version of 
gdb to use, what it is available as functionality and what not, 
and what compiler flags to use?

If there's not such a place, does it worth considering to open a 
page related to that?

- Paolo