From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11984 invoked by alias); 5 Oct 2005 19:54:43 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 11969 invoked by uid 22791); 5 Oct 2005 19:54:41 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 05 Oct 2005 19:54:41 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1ENFLb-0003Tz-1Q; Wed, 05 Oct 2005 15:54:39 -0400 Date: Wed, 05 Oct 2005 19:54:00 -0000 From: Daniel Jacobowitz To: David Lecomber Cc: gdb Subject: Re: ptrace PEEKTEXT IO error?! Message-ID: <20051005195438.GA13350@nevyn.them.org> Mail-Followup-To: David Lecomber , gdb References: <1128531841.21837.96.camel@delmo.priv.wark.uk.streamline-computing.com> <20051005171106.GA7835@nevyn.them.org> <1128536411.21837.123.camel@delmo.priv.wark.uk.streamline-computing.com> <20051005184121.GA10564@nevyn.them.org> <1128542780.3071.7.camel@cpc2-oxfd8-3-0-cust199.oxfd.cable.ntl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1128542780.3071.7.camel@cpc2-oxfd8-3-0-cust199.oxfd.cable.ntl.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-10/txt/msg00018.txt.bz2 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. -- Daniel Jacobowitz CodeSourcery, LLC