gdb seg violation during print command

David Cogen cogen@ll.mit.edu
Fri May 5 09:00:00 GMT 2000


> 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.

If the bug is elsewhere than gdb should be able to report an error message,
not seg fault itself.

Do you have any insight as to where the bug would be? g++? SunOS?

-- DavidC


More information about the Gdb mailing list