From: Tom Tromey <tromey@redhat.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [rfc] python API exposing inferior's frame stack.
Date: Mon, 30 Mar 2009 19:57:00 -0000 [thread overview]
Message-ID: <m3myb2lsq1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1238440534.11528.2.camel@localhost.localdomain> (Thiago Jung Bauermann's message of "Mon\, 30 Mar 2009 16\:15\:33 -0300")
>>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
Tom> I think symbols are assumed to use the host encoding.
Thiago> Are they? This really surprises me, since symbols are obtained from the
Thiago> executable file. Or the symbol reading mechanism converts them from
Thiago> target to host encoding?
I think this is a bit of a weird area in gdb. From what I can tell,
symbol readers don't convert between encodings. So, I think if
symbols are actually encoded in some other encoding, we'll do the
wrong thing eventually.
Anyway, gdb definitely does currently assume that symbols are in the
host encoding. E.g., the other caller of find_frame_funname calls
fprintf_symbol_filtered, which may print the argument string directly.
Tom
next prev parent reply other threads:[~2009-03-30 19:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 18:00 Thiago Jung Bauermann
2009-03-10 23:37 ` Eli Zaretskii
2009-03-15 18:35 ` Thiago Jung Bauermann
2009-03-15 19:30 ` Eli Zaretskii
2009-03-16 3:36 ` Thiago Jung Bauermann
2009-03-16 4:07 ` Eli Zaretskii
2009-03-20 23:04 ` Thiago Jung Bauermann
2009-03-21 8:34 ` Eli Zaretskii
2009-03-30 5:33 ` Thiago Jung Bauermann
2009-03-30 18:35 ` Eli Zaretskii
2009-03-30 19:09 ` Tom Tromey
2009-03-30 19:24 ` Thiago Jung Bauermann
2009-03-30 19:57 ` Tom Tromey [this message]
2009-03-30 20:50 ` Thiago Jung Bauermann
2009-03-22 16:00 ` Tom Tromey
2009-03-17 21:13 ` Tom Tromey
2009-03-17 22:43 ` Eli Zaretskii
2009-03-18 0:35 ` Tom Tromey
2009-03-18 4:12 ` Eli Zaretskii
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=m3myb2lsq1.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=bauerman@br.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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