From: "Andrew Burgess" <aburgess@broadcom.com>
To: gdb-patches@sourceware.org
Cc: "Tom Tromey" <tromey@redhat.com>,
"Andreas Schwab" <schwab@linux-m68k.org>,
Paul_Koning@Dell.com
Subject: Re: [PATCH] Don't call strchr with the NULL character.
Date: Tue, 16 Jul 2013 21:16:00 -0000 [thread overview]
Message-ID: <51E5B817.5010400@broadcom.com> (raw)
In-Reply-To: <871u6yl84c.fsf@fleche.redhat.com>
On 16/07/2013 6:36 PM, Tom Tromey wrote:
>>>>>> "Andrew" == Andrew Burgess <aburgess@broadcom.com> writes:
>
> Andrew> That said, my patch (I believe) fixes gdb given the /current/
> Andrew> behaviour, which I thought was undefined, but is in fact well
> Andrew> defined. Either way I believe this patch is required.
>
> I agree. The patch is ok.
Committed.
Thanks,
Andrew
prev parent reply other threads:[~2013-07-16 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 16:15 Andrew Burgess
2013-07-11 16:24 ` Andreas Schwab
2013-07-11 16:48 ` Paul_Koning
2013-07-12 9:18 ` Andrew Burgess
2013-07-16 17:36 ` Tom Tromey
2013-07-16 21:16 ` Andrew Burgess [this message]
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=51E5B817.5010400@broadcom.com \
--to=aburgess@broadcom.com \
--cc=Paul_Koning@Dell.com \
--cc=gdb-patches@sourceware.org \
--cc=schwab@linux-m68k.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