This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: unable to debug remotely with threads on ppc target with gdb6.1/6.3
- From: Daniel THOMPSON <daniel dot thompson at st dot com>
- To: Claudia Salzberg <salzberg at us dot ibm dot com>
- Cc: drow at false dot org, gdb at sources dot redhat dot com
- Date: Tue, 12 Apr 2005 08:52:38 +0100
- Subject: Re: unable to debug remotely with threads on ppc target with gdb6.1/6.3
- Organization: STMicroelectronics (R&D) Ltd
- References: <OFCCB63717.53F52E0C-ON87256FE0.005A0648-86256FE0.005A92EB@us.ibm.com>
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 ;-)
--
Daniel Thompson (STMicroelectronics) <daniel.thompson@st.com>
1000 Aztec West, Almondsbury, Bristol, BS32 4SQ. 01454 462659
If a car is a horseless carriage then is a motorcycle a horseless horse?