Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: David Lecomber <david@lecomber.net>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: Whacky ia64: linux_proc_xfer_partial and lseek vs pread64
Date: Fri, 10 Feb 2006 19:00:00 -0000	[thread overview]
Message-ID: <jewtg3m43c.fsf@sykes.suse.de> (raw)
In-Reply-To: <20060210181441.GA29255@nevyn.them.org> (Daniel Jacobowitz's 	message of "Fri, 10 Feb 2006 13:14:41 -0500")

Daniel Jacobowitz <drow@false.org> writes:

> On Fri, Feb 10, 2006 at 07:04:51PM +0100, Andreas Schwab wrote:
>> pread and lseek with SEEK_SET do not allow negative offsets.  lseek on
>> /proc/$$/mem is a special exception.
>
> Uh-oh.  Should pread have the same exception, or must we fall back to
> lseek?

pread fails upfront with offset < 0, whereas lseek lets the filesystem
llseek function decide.  But a fallback wouldn't help here anyway, because
you can't read the vdso memory with read, only with ptrace.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2006-02-10 19:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10 17:15 David Lecomber
2006-02-10 17:24 ` Daniel Jacobowitz
2006-02-10 18:05 ` Andreas Schwab
2006-02-10 18:14   ` Daniel Jacobowitz
2006-02-10 19:00     ` Andreas Schwab [this message]
2006-02-10 19:06       ` Daniel Jacobowitz
2006-02-11 16:22         ` Andreas Schwab
2006-02-11 16:50         ` Andreas Schwab
2006-02-11 18:26           ` Daniel Jacobowitz

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=jewtg3m43c.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=david@lecomber.net \
    --cc=gdb@sources.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