From: LeakyStain <leakstan@erols.com>
To: gdb@sources.redhat.com
Subject: Re: displaying wchar_t in gdb
Date: Thu, 22 Nov 2001 09:19:00 -0000 [thread overview]
Message-ID: <3C057546.17E07927@erols.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1011126140745.12758B-100000@is>
Ada (the programming language) supports wide characters natively, and
the GNU Ada compiler GNAT provides a patch to gdb. I haven't checked,
but I bet it prints wide character strings properly. So looking at the
GNAT patch to gdb would be a place to start.
-- Stephe
Eli Zaretskii wrote:
>
> On 26 Nov 2001, Klaus-Georg Adams wrote:
>
> > What would be a strategy to implement this natively in gdb? Can you
> > tell inside gdb if we are working with wchar_t? Should there be a
> > separate format for this?
>
> I'm not even sure this is feasible, taking the cross-debugging into
> consideration. I guess it's possible in native debugging, assuming GDB
> and the debuggee use compatible libraries for wide character support,
> and support the same character sets.
>
> If it _is_ possible and feasible, then a special format is probably the
> way to go.
WARNING: multiple messages have this Message-ID
From: LeakyStain <leakstan@erols.com>
To: gdb@sources.redhat.com
Subject: Re: displaying wchar_t in gdb
Date: Wed, 28 Nov 2001 15:38:00 -0000 [thread overview]
Message-ID: <3C057546.17E07927@erols.com> (raw)
Message-ID: <20011128153800.zHN9eANOPoai7zCQ46rLhmC1z-yZ9Mdoo3BzDwh0g5g@z> (raw)
In-Reply-To: <Pine.SUN.3.91.1011126140745.12758B-100000@is>
Ada (the programming language) supports wide characters natively, and
the GNU Ada compiler GNAT provides a patch to gdb. I haven't checked,
but I bet it prints wide character strings properly. So looking at the
GNAT patch to gdb would be a place to start.
-- Stephe
Eli Zaretskii wrote:
>
> On 26 Nov 2001, Klaus-Georg Adams wrote:
>
> > What would be a strategy to implement this natively in gdb? Can you
> > tell inside gdb if we are working with wchar_t? Should there be a
> > separate format for this?
>
> I'm not even sure this is feasible, taking the cross-debugging into
> consideration. I guess it's possible in native debugging, assuming GDB
> and the debuggee use compatible libraries for wide character support,
> and support the same character sets.
>
> If it _is_ possible and feasible, then a special format is probably the
> way to go.
next prev parent reply other threads:[~2001-11-28 23:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 16:57 Klaus-Georg Adams
2001-11-26 1:16 ` Klaus-Georg Adams
2001-11-26 1:29 ` Eli Zaretskii
2001-11-13 21:23 ` Eli Zaretskii
2001-11-26 1:59 ` Klaus-Georg Adams
2001-11-13 21:28 ` Klaus-Georg Adams
2001-11-26 4:11 ` Eli Zaretskii
2001-11-13 23:51 ` Eli Zaretskii
2001-11-22 9:19 ` LeakyStain [this message]
2001-11-28 15:38 ` LeakyStain
2001-11-22 14:30 ` Tom Tromey
2001-11-28 16:02 ` Tom Tromey
2001-11-29 0:19 ` Eli Zaretskii
2001-11-23 13:27 ` Eli Zaretskii
2001-11-24 22:42 ` Tom Tromey
2001-11-29 8:04 ` Tom Tromey
2001-11-25 10:38 Klaus-Georg Adams
2001-11-25 10:44 ` Arnaud Charlet
2001-11-30 2:22 ` Arnaud Charlet
2001-11-25 12:10 ` Paul Hilfinger
2001-11-30 3:36 ` Paul Hilfinger
2001-11-30 2:15 ` Klaus-Georg Adams
2001-11-30 2:25 ` Joel Brobecker
2001-11-25 10:54 ` Joel Brobecker
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=3C057546.17E07927@erols.com \
--to=leakstan@erols.com \
--cc=gdb@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