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: Mark Kettenis <kettenis at wins dot uva dot nl>
- Subject: Re: gdb seg violation during print command
- From: Daniel Berlin <dan at cgsoftware dot com>
- Date: 03 May 2000 17:10:37 -0400
- Cc: dan at cgsoftware dot com, gdb at sourceware dot cygnus dot com
- References: <200005031637.MAA25467@ll.mit.edu><200005031759.TAA18350@landau.wins.uva.nl><snvze4ib.fsf@dynamic-addr-88-117.resnet.rochester.edu><200005032105.e43L5U300694@delius.kettenis.local>
- Reply-To: dan at cgsoftware dot com
Mark Kettenis <kettenis@wins.uva.nl> writes:
> >
>
> What version of gdb is this really? IE when is it from?
> (We've had 20000204 there forever).
>
> April 25. But I just tested it with a GDB compiled from sources
> checked out of CVS half an our ago. No difference.
Okay. And you said egcs 1.1.2, right?
Please "set debug overload 1" and retry, and send me the results.
I suspect the problem is that that version of egcs is marking types with
the wrong sign in the debug info in certain cases, and the
rank_one_type code isn't handling the specific case, and defaulting to
saying it's an incompatible overload.
I ran into this problem once before, and had patches to deal with
these specific comparisons in rank_one_type, but i seem to have lost
them during a file system screwup (I did them in early january).
They were trivial, and i can redo them.
But first, i need to make sure that's the problem.
>
> Mark