From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19362 invoked by alias); 5 Oct 2005 17:11:10 -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 19353 invoked by uid 22791); 5 Oct 2005 17:11:09 -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 17:11:09 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1ENCnK-00022z-Sz; Wed, 05 Oct 2005 13:11:06 -0400 Date: Wed, 05 Oct 2005 17:11:00 -0000 From: Daniel Jacobowitz To: David Lecomber Cc: gdb Subject: Re: ptrace PEEKTEXT IO error?! Message-ID: <20051005171106.GA7835@nevyn.them.org> Mail-Followup-To: David Lecomber , gdb References: <1128531841.21837.96.camel@delmo.priv.wark.uk.streamline-computing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1128531841.21837.96.camel@delmo.priv.wark.uk.streamline-computing.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-10/txt/msg00011.txt.bz2 On Wed, Oct 05, 2005 at 06:04:00PM +0100, David Lecomber wrote: > Dear all, > > I have a multithreaded code which is misbehaving in GDB (verified on > latest CVS). After threads are created, the target suddenly seems to > become unwriteable, and even unreadable in some bits. This usually means the thread is not stopped. Failing that, check with your kernel. > If I then strace the running GDB, I see the following errors (and a few > more ptrace errors).. > > ptrace(PTRACE_PEEKTEXT, 17994, 0x407480, [0]) = -1 EIO (Input/output > error) > ptrace(PTRACE_POKEDATA, 17994, 0x407480, 0xffffffffffffccff) = -1 EIO > (Input/output error) -- Daniel Jacobowitz CodeSourcery, LLC