From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6197 invoked by alias); 12 Apr 2005 12:06:34 -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 6159 invoked from network); 12 Apr 2005 12:06:25 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 12 Apr 2005 12:06:25 -0000 Received: from drow by nevyn.them.org with local (Exim 4.50 #1 (Debian)) id 1DLK9s-0001pA-Rv; Tue, 12 Apr 2005 08:06:20 -0400 Date: Tue, 12 Apr 2005 12:06:00 -0000 From: Daniel Jacobowitz To: Daniel THOMPSON Cc: Claudia Salzberg , gdb@sources.redhat.com Subject: Re: unable to debug remotely with threads on ppc target with gdb6.1/6.3 Message-ID: <20050412120620.GA6951@nevyn.them.org> Mail-Followup-To: Daniel THOMPSON , Claudia Salzberg , gdb@sources.redhat.com References: <425B7E46.8040408@st.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <425B7E46.8040408@st.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-04/txt/msg00061.txt.bz2 On Tue, Apr 12, 2005 at 08:52:38AM +0100, Daniel THOMPSON wrote: > Claudia Salzberg wrote: > >I have tried both gdb 6.1 the latest version (6.3) and am trying to debug > >a simple threaded program using pthreads remotely. The target board is a > >440GP and the host is an x86 box. I see references to similar problems in > >past posts from 12 2004 ( > >http://sourceware.org/ml/gdb/2004-12/msg00028.html) but did not see if a > >patch was created. > > No I am not aware of any patch fixing this issue. > > The problem (as the thread says) is that ps_lgetregs is not implemented > inside the gdbserver on PPC (or any other machine that uses > PEEKUSER/POKEUSER to access its register sets). > > You should be able to jury rig a version by copying the code in > ppc-linux-nat.c:fill_gregset() into the ps_lgetregs function and > modifying the code to target the gdbserver register cache rather then > the gdb register cache. > > There is, of course, a proper to way to do the above but you might want > to confirm the above works first ;-) That's not Claudia's problem; the above only applies to NPTL, and she appears to be using LinuxThreads from the error logs. -- Daniel Jacobowitz CodeSourcery, LLC