gdb seg violation during print command
Daniel Berlin
dan@cgsoftware.com
Fri May 5 09:49:00 GMT 2000
David Cogen <cogen@ll.mit.edu> writes:
> > I can almost guarantee this is not a gdb bug.
> > Compiled with both dwarf2 debug info, and stabs debug info, it works fine
> > on BeOS and linux.
>
> But a gdb seg violation is a gdb bug by definition, I would think.
Yes, if that bug still occurs.
:)
>
> If the bug is elsewhere than gdb should be able to report an error message,
> not seg fault itself.
Right.
>
> Do you have any insight as to where the bug would be? g++? SunOS?
It's very hard to say.
>
> -- DavidC
More information about the Gdb
mailing list