Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [patch] python: save/restore/fix error state
Date: Wed, 13 Oct 2010 13:28:00 -0000	[thread overview]
Message-ID: <20101013132810.GA24601@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3y6a3gkg9.fsf@fleche.redhat.com>

On Tue, 12 Oct 2010 23:39:02 +0200, Tom Tromey wrote:
> I don't have a strong feeling either way.

Checked-in the error existing version providing back(forward)traces as IMO
such case is already a problem and it should not be difficult to track it
down:
	http://sourceware.org/ml/gdb-cvs/2010-10/msg00082.html


> This IBM1047 scenario is far-fetched.

I have to note this problem occurs for 882 (75.51%) out of the 1168 charsets
supported by glibc.


Thanks,
Jan


  reply	other threads:[~2010-10-13 13:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08 19:12 [patch] python(+solib error): save/restore " Jan Kratochvil
2010-10-08 20:08 ` Doug Evans
2010-10-08 20:20   ` Doug Evans
2010-10-08 21:27     ` Tom Tromey
2010-10-08 21:35       ` Doug Evans
2010-10-09 20:40   ` [patch] python: save/restore/fix " Jan Kratochvil
2010-10-12 19:55     ` Tom Tromey
2010-10-12 21:08       ` Jan Kratochvil
2010-10-12 21:39         ` Tom Tromey
2010-10-13 13:28           ` Jan Kratochvil [this message]
2010-10-13 15:38             ` Tom Tromey
2010-10-13 15:58               ` Jan Kratochvil
2010-10-13 18:46                 ` 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=20101013132810.GA24601@host1.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dje@google.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