This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: gdb/256: cannot print values of some integer class members
- 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: 13 Dec 2001 15:58:01 -0000
- Subject: Re: gdb/256: cannot print values of some integer class members
- Reply-to: Daniel Jacobowitz <drow at mvista dot com>
The following reply was made to PR gdb/256; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@mvista.com>
To: mprisco@ubspw.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/256: cannot print values of some integer class members
Date: Thu, 13 Dec 2001 10:53:10 -0500
Patches for this have been posted, and should be committed soon.
On Thu, Dec 13, 2001 at 02:09:12PM -0000, mprisco@ubspw.com wrote:
>
> >Number: 256
> >Category: gdb
> >Synopsis: cannot print values of some integer class members
> >Confidential: no
> >Severity: serious
> >Priority: high
> >Responsible: unassigned
> >State: open
> >Class: sw-bug
> >Submitter-Id: net
> >Arrival-Date: Thu Dec 13 06:18:00 PST 2001
> >Closed-Date:
> >Last-Modified:
> >Originator: Marc Prisco
> >Release: gdb-5.1
> >Organization:
> >Environment:
> gdb5.1 build on ultra sparc 5 running solaris 8
> >Description:
> Occasionally, whenever I try to print the value of an integer
> I receive the following:
>
> (gdb) p widestRow
> Value can't be converted to integer.
>
> where widestRow in a rpivate integer member of report.
> Unfortunately, whenever I try to isolate problem into
> a smaller test program, this behavior ceases.
>
> When I look at gdb in the debugger, I see the message is
> generated in values.c:659. Interestingly
> there code is TYPE_CODE_STRUCT. Although I don't see the
> problem this doesn't seem quite right.
> >How-To-Repeat:
>
> >Fix:
>
> >Release-Note:
> >Audit-Trail:
> >Unformatted:
>
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer