From: Daniel Jacobowitz <drow@false.org>
To: Andre Ancelin <andrea@adtecinc.com>
Cc: gdb@sources.redhat.com, cagney@gnu.org
Subject: Re: gdbserver breakpoint problem with PowerPC
Date: Thu, 01 Apr 2004 20:52:00 -0000 [thread overview]
Message-ID: <20040401205213.GA6872@nevyn.them.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2004-04-01 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 20:46 Andre Ancelin
2004-04-01 20:52 ` Daniel Jacobowitz [this message]
2004-04-02 0:33 ` Andre Ancelin
2004-04-02 1:17 ` Daniel Jacobowitz
2004-04-02 18:13 ` Andre Ancelin
2004-04-02 18:48 ` Mark Salter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040401205213.GA6872@nevyn.them.org \
--to=drow@false.org \
--cc=andrea@adtecinc.com \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox