This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: gdb seg violation during print command
- To: David Cogen <cogen at ll dot mit dot edu>
- Subject: Re: gdb seg violation during print command
- From: Daniel Berlin <dan at cgsoftware dot com>
- Date: 05 May 2000 12:49:14 -0400
- Cc: dan at cgsoftware dot com, kettenis at wins dot uva dot nl,gdb at sourceware dot cygnus dot com, cogen at poblano dot resnet dot rochester dot edu
- References: <200005051556.LAA26727@ll.mit.edu>
- Reply-To: dan at cgsoftware dot com
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