What's the proper way to debug D programs with GDB?
b.helyer at gmail.com
Thu Mar 18 16:22:52 PDT 2010
On 19/03/10 04:59, Robert Clipsham wrote:
> On 18/03/10 04:23, grauzone wrote:
>> Bernard Helyer wrote:
>>> I have definitely had programs choke up gdb even when using the `-gc`
>>> flag. I'll have a poke around tonight and see what I can find.
>> Me too, but always in larger amounts of code, where it's hopeless to try
>> to find the exact location. It's probably caused by a single obscure D
> If either of you can manage to come up with a test case that fails with
> -gc, even if it's huge, let me know and I'll see if I can figure out
> what's happening :)
Okay got it. It's 6000 lines and six megabytes large (and hacked to all
hell, as the std.string templates started breaking, for some reason),
but it doesn't debug with `-gc`! What's the best way to get it to you?
More information about the Digitalmars-d-debugger