From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16735 invoked by alias); 1 Apr 2004 20:52:18 -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 16656 invoked from network); 1 Apr 2004 20:52:16 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 1 Apr 2004 20:52:16 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1B99Ab-0001tI-Pc; Thu, 01 Apr 2004 15:52:13 -0500 Date: Thu, 01 Apr 2004 20:52:00 -0000 From: Daniel Jacobowitz To: Andre Ancelin Cc: gdb@sources.redhat.com, cagney@gnu.org Subject: Re: gdbserver breakpoint problem with PowerPC Message-ID: <20040401205213.GA6872@nevyn.them.org> Mail-Followup-To: Andre Ancelin , gdb@sources.redhat.com, cagney@gnu.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2004-04/txt/msg00006.txt.bz2 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