Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Andrew Burgess" <aburgess@broadcom.com>
Cc: gdb-patches@sourceware.org,
	"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 17:36:00 -0000	[thread overview]
Message-ID: <871u6yl84c.fsf@fleche.redhat.com> (raw)
In-Reply-To: <51DFC9C6.2060806@broadcom.com> (Andrew Burgess's message of	"Fri, 12 Jul 2013 10:17:58 +0100")

>>>>> "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.

thanks,
Tom


  reply	other threads:[~2013-07-16 17:36 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 [this message]
2013-07-16 21:16     ` Andrew Burgess

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=871u6yl84c.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=Paul_Koning@Dell.com \
    --cc=aburgess@broadcom.com \
    --cc=gdb-patches@sourceware.org \
    --cc=schwab@linux-m68k.org \
    /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