From: David Lecomber <david@allinea.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: ptrace PEEKTEXT IO error?!
Date: Wed, 05 Oct 2005 20:31:00 -0000 [thread overview]
Message-ID: <1128545245.3071.9.camel@cpc2-oxfd8-3-0-cust199.oxfd.cable.ntl.com> (raw)
In-Reply-To: <20051005195438.GA13350@nevyn.them.org>
On Wed, 2005-10-05 at 15:54 -0400, Daniel Jacobowitz wrote:
> On Wed, Oct 05, 2005 at 09:06:20PM +0100, David Lecomber wrote:
> >
> > > >
> > > > It seems ok at reading memory from addresses on the heap and stack --
> > > > but it barfs at reading memory from the text segment. [snip]
> >
> > > No, this is most likely a kernel bug. This is mapped code, right, not
> > > some mmaped device file (which is not generally accessible by ptrace)?
> >
> > The code I'm trying to read is an ordinary subroutine in an ordinary C
> > file. The program does call a library handling infiniband network
> > cards, and there are loads of kernel modules on this machine looking
> > after that.
>
> The infiniband code does all sorts of funky things to VM. It's
> extremely likely that this is repsonsible.
Great, I bet this bug'll cheer them up! Thanks for the info, I'll chase
their mailing list now.
Cheers
David
prev parent reply other threads:[~2005-10-05 20:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 17:10 David Lecomber
2005-10-05 17:11 ` Daniel Jacobowitz
2005-10-05 18:26 ` David Lecomber
2005-10-05 18:40 ` David Lecomber
2005-10-05 18:41 ` Daniel Jacobowitz
2005-10-05 19:50 ` David Lecomber
2005-10-05 19:54 ` Daniel Jacobowitz
2005-10-05 20:31 ` David Lecomber [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=1128545245.3071.9.camel@cpc2-oxfd8-3-0-cust199.oxfd.cable.ntl.com \
--to=david@allinea.com \
--cc=drow@false.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).