Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@codesourcery.com>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: fix remote-fileio breakage
Date: Tue, 18 Jul 2006 20:47:00 -0000	[thread overview]
Message-ID: <20060718204752.GC27666@nevyn.them.org> (raw)
In-Reply-To: <44BC9088.4070700@codesourcery.com>

On Tue, Jul 18, 2006 at 08:40:56AM +0100, Nathan Sidwell wrote:
> It appears that recent changes to remote protocol handling have exposed a 
> latent bug in remote fileio.  Two of the remote fileio calls start reading 
> target memory before completely processing the fileio response packet.  
> Reading remote memory overwrites that buffer.

Yeah, you're right.

> 2006-07-18  Nathan Sidwell  <nathan@codesourcery.com>
> 
> 	* remote-fileio.c (remote_fileio_func_rename): Reorder to process
> 	input buffer before reading memory.
> 	(remote_fileio_func_stat): Likewise.

OK, thanks.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2006-07-18 20:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18  7:40 Nathan Sidwell
2006-07-18 20:47 ` Daniel Jacobowitz [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=20060718204752.GC27666@nevyn.them.org \
    --to=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nathan@codesourcery.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