This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gdbserver breakpoint problem with PowerPC
- From: Daniel Jacobowitz <drow at false dot org>
- To: Andre Ancelin <andrea at adtecinc dot com>
- Cc: gdb at sources dot redhat dot com, cagney at gnu dot org
- Date: Thu, 1 Apr 2004 15:52:13 -0500
- Subject: Re: gdbserver breakpoint problem with PowerPC
- References: <LOEGKAKLCNEBNKEDOOGNKEIFDKAA.andrea@adtecinc.com>
On Thu, Apr 01, 2004 at 02:51:07PM -0500, Andre Ancelin wrote:
> Hi everyone!
>
> I'm having a problem with gdbserver 6.0. Setup:
>
> HOST- x86 (P4), SuSE 8.0 distro, gdb 6.0
> TARGET- PowerPC405GP (custom board), 2.4.21 PPC kernel (custom), gdbserver
> 6.0 w/ libthread_db.so.1 dependency.
> TOOLCHAIN- binutil 2.11.2, gcc 2.95.3, glibc(-linuxthreads) 2.2.2
>
> The problem: the target does not reliably set breakpoints. Single step works
> once, then the next step takes off and continues. Set two consecutive
> breakpoints and target may or may not stop at first, but never stops at
> second. Apparently, gdbserver is not always setting up the trap. I have
> captured the remote protocol and see that the single step command is both
> sent and acknowledged ($s#73...Ack) for both the case where a single step
> works and doesn't.
If GDB sends an 's' packet, gdbserver will issue a PTRACE_SINGLESTEP
request. If that loses control, then your kernel has failed to
implement PTRACE_SINGLESTEP correctly; take it up with your kernel.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer