This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: c++/1084: set print object on does not work correctly in some cases
- 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: 21 Feb 2003 21:58:01 -0000
- Subject: Re: c++/1084: set print object on does not work correctly in some cases
- Reply-to: Daniel Jacobowitz <drow at mvista dot com>
The following reply was made to PR c++/1084; it has been noted by GNATS.
From: Daniel Jacobowitz <drow at mvista dot com>
To: salman dot khilji at cae dot com
Cc: gdb-gnats at sources dot redhat dot com
Subject: Re: c++/1084: set print object on does not work correctly in some cases
Date: Fri, 21 Feb 2003 16:57:34 -0500
On Fri, Feb 21, 2003 at 09:21:48PM -0000, salman dot khilji at cae dot com wrote:
>
> >Number: 1084
> >Category: c++
> >Synopsis: set print object on does not work correctly in some cases
> >Confidential: no
> >Severity: critical
> >Priority: medium
> >Responsible: unassigned
> >State: open
> >Class: sw-bug
> >Submitter-Id: net
> >Arrival-Date: Fri Feb 21 21:28:00 UTC 2003
> >Closed-Date:
> >Last-Modified:
> >Originator: Salman Khilji
> >Release: GDB 5.1.1
> >Organization:
> >Environment:
> gcc 2.95.3 in SuSE Linux 8.0
> >Description:
> I suppose a picture would describe the bug better than words, so here it is:
>
> (gdb) print b1
> $1 = (Base *) 0x804a4a0
> (gdb) print b2
> $2 = (Base_2 *) 0x804a4cc
> (gdb) print b3
> $3 = (Base_3 *) 0x401b9bd8
> (gdb) set print object on
> (gdb) print b1
> Cannot access memory at address 0x4
> (gdb) print b2
> $4 = (virtual baseclass botch
> (gdb) print b3
> $5 = (suspicious *) 0x401b9bd8
GDB 5.1.1 is pretty old, and I fixed a virtual baseclass botch bug
recently. Could you please get GDB 5.3 from sources.redhat.com and try
this experiment again?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer