From: Tom Tromey <tromey@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Michael Snyder <msnyder@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: Patch: printing java `char' values
Date: Wed, 08 May 2002 13:32:00 -0000 [thread overview]
Message-ID: <878z6umkwn.fsf@creche.redhat.com> (raw)
In-Reply-To: Daniel Jacobowitz's message of "Wed, 8 May 2002 15:47:46 -0400"
>>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
Daniel> Soemthing interesting is going on here... I'd like to know how
Daniel> it works in the stabs case. Tom, could you compile your test
Daniel> with -gstabs+ and step through the char printing code? When I
Daniel> do that, 'c' has TYPE_CODE_CHAR set anyway, even though the
Daniel> stabs reader marked it as TYPE_CODE_INT. It'd be nice to
Daniel> figure out where that magic happens.
When I use -gstabs+ the type looks like this:
(gdb) p *type
$1 = {
code = TYPE_CODE_CHAR,
name = 0x83e6574 "char",
tag_name = 0x0,
length = 2,
upper_bound_type = 0,
lower_bound_type = 0,
objfile = 0x0,
target_type = 0x0,
pointer_type = 0x0,
reference_type = 0x0,
cv_type = 0x83d4980,
as_type = 0x83d4980,
flags = 1,
nfields = 0,
fields = 0x0,
vptr_basetype = 0x0,
vptr_fieldno = -1,
type_specific = {
arg_types = 0x0,
cplus_stuff = 0x0,
floatformat = 0x0
}
}
HTH,
Tom
next prev parent reply other threads:[~2002-05-08 20:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 10:11 Tom Tromey
2002-05-06 17:05 ` Michael Snyder
2002-05-07 13:29 ` Tom Tromey
2002-05-07 15:45 ` Andrew Cagney
2002-05-07 13:43 ` Daniel Jacobowitz
2002-05-07 14:22 ` Michael Snyder
2002-05-07 14:35 ` Tom Tromey
2002-05-08 12:12 ` Michael Snyder
2002-05-08 12:47 ` Daniel Jacobowitz
2002-05-08 13:32 ` Tom Tromey [this message]
2002-05-08 13:46 ` Daniel Jacobowitz
2002-05-08 14:10 ` Michael Snyder
2002-05-08 14:20 ` Daniel Jacobowitz
2002-05-08 15:39 ` Michael Snyder
2002-05-08 15:42 ` Tom Tromey
2002-05-08 16:52 ` Michael Snyder
2002-05-08 21:09 ` Tom Tromey
2002-05-09 11:09 ` Michael Snyder
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=878z6umkwn.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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