This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: c++/1251: GDB crash
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 23 Jun 2003 14:18:01 -0000
- Subject: Re: c++/1251: GDB crash
- Reply-to: Daniel Jacobowitz <drow at mvista dot com>
The following reply was made to PR c++/1251; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@mvista.com>
To: adarovsky@mail.ru
Cc: gdb-gnats@sources.redhat.com
Subject: Re: c++/1251: GDB crash
Date: Mon, 23 Jun 2003 08:49:18 -0400
On Mon, Jun 23, 2003 at 04:21:20AM -0000, adarovsky@mail.ru wrote:
>
> >Number: 1251
> >Category: c++
> >Synopsis: GDB crash
> >Confidential: no
> >Severity: critical
> >Priority: medium
> >Responsible: unassigned
> >State: open
> >Class: sw-bug
> >Submitter-Id: net
> >Arrival-Date: Mon Jun 23 04:28:00 UTC 2003
> >Closed-Date:
> >Last-Modified:
> >Originator: Alexander Darovsky
> >Release: latest cvs
> >Organization:
> >Environment:
> linux i686
> >Description:
> In gnu-v3-abi.c:417 sanity measure crashes gdb when
> TYPE_VPTR_FIELDNO (vbasetype) returns -1.
> It happens sometimes in the big project, so I cannot give you a source.
> But if I comment lines conserning this check, everything works ok...
I'll fix the segfault. I've been meaning to do that for a while.
> P.S. What -1 means? Is it a C++ ABI bug?
It's a bug somewhere else in GDB - it should never return -1. A
testcase would be appreciated.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer