Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Chris January <chris.january@allinea.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix incorrect use of strcpy.
Date: Fri, 16 Mar 2012 11:20:00 -0000	[thread overview]
Message-ID: <1331896807.2787.3.camel@gumtree> (raw)
In-Reply-To: <874ntznej0.fsf@fleche.redhat.com>

On Thu, 2012-03-08 at 11:17 -0700, Tom Tromey wrote:
> >>>>> "Chris" == Chris January <chris.january@allinea.com> writes:
> 
> Chris> The strings passed to strcpy may not overlap, but &p and &p[len + 1]
> Chris> clearly do. memmove allows overlapping memory area.

Ping for commit?

> I think you should get started on your copyright assignment papers.
> Your current patches are probably under the limit, but if you send more
> then we'll need these.

We have a company-wide assignment on file.

Chris



  reply	other threads:[~2012-03-16 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08 14:21 Chris January
2012-03-08 18:17 ` Tom Tromey
2012-03-16 11:20   ` Chris January [this message]
2012-03-16 18:20     ` 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=1331896807.2787.3.camel@gumtree \
    --to=chris.january@allinea.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