What is the best version of gdb to use (with D, need I say?)

Where are the patches for using gdb with D?

Thanks,

Ant

There is a patch on dsource.org for GDB version 6.3.  All it does it symbol demangling, but it's a start.

~John Demme

Ant wrote:

> What is the best version of gdb to use (with D, need I say?)
> 
> Where are the patches for using gdb with D?
> 
> Thanks,
> 
> Ant

In article <duoglr$22hf$1@digitaldaemon.com>, John Demme says...
>
>There is a patch on dsource.org for GDB version 6.3.  All it does it symbol demangling, but it's a start.
>

dsource, I browsed through it but missed it. I'll more look carefully. But I'm not sure all 6.3 is good. is it? I'll try the latest 6.3.

I was using 6.4 until yesterday it segfault (gdb it self).

Ant

> I was using 6.4 until yesterday it segfault (gdb it self).

I had this problem too.
I reduced the code to make a bug report. But it turn out that
uncommenting a function out and the segfault was gone.
It could add a function to that module at any point a gdb segfaults.
But because it was still a big program i didn't made the bug report.
A backtrace of gdb itself brought the segfault in dwarf2_read...
Both segfaulted, the unpatched 6.4 debian and the d-patched 6.3.

Frank

Please post a bug report on the GDB Patches forum over at dsource.org/forums.  Please include the backtrace of gdb's crash as well as the code that you're compiling (if possible).  If it's part of a large codebase, and you're willing to work with me, we'll discuss it over at dsource.

I've had some issues with this, but haven't been able to track it down yet, and it hasn't been enough of a nusance to put a ton of time into it.  I'm not surprised that an unpatched GDB crashed, since it generally can't handle the D DWARF signature.

~John Demme

Frank Benoit wrote:

> 
>> I was using 6.4 until yesterday it segfault (gdb it self).
> 
> I had this problem too.
> I reduced the code to make a bug report. But it turn out that
> uncommenting a function out and the segfault was gone.
> It could add a function to that module at any point a gdb segfaults.
> But because it was still a big program i didn't made the bug report.
> A backtrace of gdb itself brought the segfault in dwarf2_read...
> Both segfaulted, the unpatched 6.4 debian and the d-patched 6.3.
> 
> Frank

Frank Benoit wrote:

> 
>> I was using 6.4 until yesterday it segfault (gdb it self).
> 
> I had this problem too.
> I reduced the code to make a bug report. But it turn out that
> uncommenting a function out and the segfault was gone.
> It could add a function to that module at any point a gdb segfaults.
> But because it was still a big program i didn't made the bug report.
> A backtrace of gdb itself brought the segfault in dwarf2_read...
> Both segfaulted, the unpatched 6.4 debian and the d-patched 6.3.
> 
> Frank

I just tried to reply to your email and got an error: user unknown.  You do have a different email I can use?

Thanks,
John Demme

> I just tried to reply to your email and got an error: user unknown.  You do have a different email I can use?
> 
> Thanks,
> John Demme

benoit [at the domain] tionex [ dot ] de