public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
	       Andreas Schwab <schwab@redhat.com>,
	gdb-patches@sourceware.org
Subject: Re: [patch] Fix new FAIL `reject p 0x1.1' [fixup]
Date: Mon, 23 Aug 2010 19:57:00 -0000	[thread overview]
Message-ID: <AANLkTimuUUe2HKQsUNjE6cKX8NvqTs2W7CzV0UZi2M_4@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=6F-xAp7NsZJqM=W7C_bueUvmziBhhGaVoS-jh@mail.gmail.com>

On Mon, Aug 23, 2010 at 12:49 PM, Doug Evans <dje@google.com> wrote:
>> While thanks for catching it I still believe now my testcase update is the
>> appropriate fix - if glibc supports then extended input syntax let the GDB
>> user benefit from it.
>
> It's ok with me.

I should add that IWBN to have an additional testcase that exercises
sscanf (...) == 0 on newer glibcs.

  reply	other threads:[~2010-08-23 19:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17  0:31 [patch] Handle 0 result from sscanf when parsing fp values Doug Evans
2010-08-17  8:18 ` Andreas Schwab
2010-08-17 11:37   ` Doug Evans
2010-08-18 20:38     ` Doug Evans
2010-08-20  7:34       ` [patch] Fix new FAIL `reject p 0x1.1' [Re: [patch] Handle 0 result from sscanf when parsing fp values.] Jan Kratochvil
2010-08-20  7:37         ` [patch] Fix new FAIL `reject p 0x1.1' [fixup] " Jan Kratochvil
2010-08-20 11:58           ` Joseph S. Myers
2010-08-23 15:35             ` Doug Evans
2010-08-23 18:55               ` [patch] Fix new FAIL `reject p 0x1.1' [fixup] Jan Kratochvil
2010-08-23 19:49                 ` Doug Evans
2010-08-23 19:57                   ` Doug Evans [this message]
2010-08-31 19:38                     ` Jan Kratochvil
2010-08-31 22:51                       ` Doug Evans
2010-09-02 15:11                         ` Jan Kratochvil
2010-09-06 22:29                           ` Jan Kratochvil

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=AANLkTimuUUe2HKQsUNjE6cKX8NvqTs2W7CzV0UZi2M_4@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=schwab@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).