Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Andre Oliveira Loureiro do Baixo <andreolb@gmail.com>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] PR exp/9103
Date: Wed, 11 Mar 2009 20:29:00 -0000	[thread overview]
Message-ID: <1236803010.11106.50.camel@localhost.localdomain> (raw)
In-Reply-To: <c3f94bcc0903111013t41c96900v872addb65b5e31c3@mail.gmail.com>

(slightly edited to correct top-posting)

El mié, 11-03-2009 a las 14:13 -0300, Andre Oliveira Loureiro do Baixo
escribió:
> On Wed, Mar 11, 2009 at 2:08 PM, Tom Tromey <tromey@redhat.com> wrote:
> >>>>>> "Andre" == Andre Oliveira Loureiro do Baixo <andreolb@gmail.com> writes:
> >
> > Andre> The patch works correctly because the function inside the modified
> > Andre> condition (val_print_string) scans the string using the size of each
> > Andre> character of the string. This size is passed to the function using the
> > Andre> parameter TYPE_LENGTH (elttype). Char * strings are printed by this
> > Andre> function, the only difference is that wchar_t* strings didn't get
> > Andre> inside the condition, and now they do.
> >
> > Yeah, but it isn't as useful as it could be, because it doesn't
> > properly handle charset conversions.  Also, I suspect it won't work in
> > C, where wchar_t is a typedef.
> >
> > Try this patch instead:
> >
> >    http://sourceware.org/ml/gdb-patches/2009-01/msg00533.html
>
> Yes, it works in C with no problems at all.

Tromey, do you think your charset branch will make it in time for 7.0?
If not, we could consider Andre's approach...
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


  reply	other threads:[~2009-03-11 20:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c3f94bcc0903101928g3d767b7ah60ac81e8b6f77de@mail.gmail.com>
2009-03-11 15:37 ` Andre Oliveira Loureiro do Baixo
2009-03-11 16:30   ` Daniel Jacobowitz
2009-03-11 17:09     ` Andre Oliveira Loureiro do Baixo
2009-03-11 17:13       ` Tom Tromey
2009-03-11 18:37         ` Andre Oliveira Loureiro do Baixo
2009-03-11 20:29           ` Thiago Jung Bauermann [this message]
2009-03-11 22:25             ` Tom Tromey
2009-03-12  1:11               ` Tom Tromey
2009-03-13 23:37                 ` Joel Brobecker
2009-03-13 23:38                   ` Joel Brobecker
2009-03-14  1:41                     ` Tom Tromey
2009-03-14  0:10                   ` Mark Kettenis
2009-03-17 20:06                     ` Tom Tromey
2009-03-17 22:12                       ` Eli Zaretskii
2009-03-18  3:07                         ` Tom Tromey
2009-03-18  4:20                           ` Eli Zaretskii
2009-03-18 17:11                             ` Tom Tromey
2009-03-18 20:30                               ` Eli Zaretskii
2009-03-18  0:46                       ` Joel Brobecker
2009-03-18  1:14                         ` Tom Tromey

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=1236803010.11106.50.camel@localhost.localdomain \
    --to=bauerman@br.ibm.com \
    --cc=andreolb@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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