From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: RFC: Print the type of a C value in one more case
Date: Tue, 29 Mar 2005 20:37:00 -0000 [thread overview]
Message-ID: <20050329203830.GA20646@nevyn.them.org> (raw)
In-Reply-To: <BE6E4E1A.9A2C%schlie@comcast.net>
On Tue, Mar 29, 2005 at 12:13:14AM -0500, Paul Schlie wrote:
> >> Daniel Jacobowitz wrote:
> >> This is something that constantly bugs me when debugging GCC. GCC has
> >> typedefs for "tree" and "rtx" which are both pointers to structs. When
> >> you print either, you just get "$1 = 0xbf000100" without any indication
> >> of the type of the variable; but normally GDB prints types for pointers.
> >> This comes from a missing check_typedef in c_value_print.
> >>
> >> There were a couple of ways to fix it; I chose to print the typedef rather
> >> than what the typedef pointed to. The only difference in the testsuite is
> >> in one objc test, which perfectly illustrates the desired change:
> >>
> >> -$1 = 0x0
> >> +$1 = (id) 0x0
> >> ...
>
> - was there ever a conclusion on this item, it certainly seems helpful?
I never got around to committing it. Since no one disliked it, I've
checked this in now.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-29 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 20:57 Paul Schlie
2005-03-29 5:13 ` Paul Schlie
2005-03-29 20:37 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-06 17:45 Daniel Jacobowitz
2005-03-10 22:14 ` Kevin Buettner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050329203830.GA20646@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox