From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29627 invoked by alias); 7 Nov 2004 02:10:25 -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 29557 invoked from network); 7 Nov 2004 02:10:20 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 7 Nov 2004 02:10:20 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1CQcVX-000708-Uq; Sat, 06 Nov 2004 21:10:20 -0500 Date: Sun, 07 Nov 2004 02:38:00 -0000 From: Daniel Jacobowitz To: Andrew de Quincey Cc: gdb@sources.redhat.com Subject: Re: GDB 6.2.1 with powerpc platform and uclibc and user breakpoint problem Message-ID: <20041107021019.GA26731@nevyn.them.org> Mail-Followup-To: Andrew de Quincey , gdb@sources.redhat.com References: <200411061434.45201.adq_dvb@lidskialf.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200411061434.45201.adq_dvb@lidskialf.net> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-11/txt/msg00051.txt.bz2 On Sat, Nov 06, 2004 at 02:34:45PM +0000, Andrew de Quincey wrote: > -- this is the internal breakpoint on _dl_debug_state being triggered. I see this in my kernel > tracing in the trap handlers. > > RX: m10000548,4 > TX: 7d821008 > RX: M10000548,4:38000000 > TX: OK > RX: m300018d4,4 > TX: 7d821008 > RX: M300018d4,4:801c005c > TX: OK > > -- GDB is clearing the breakpoints *INCLUDING MY USER BREAKPOINT* - it has removed the > trap instruction and set it back to 0x38000000. why is it doing this!?! So that it can step past the breakpoint. > RX: m10010904,b0 > TX: 00000001000000010000000c1000036c0000000d1000089c000000041000012800000005100002680000000610000 > RX: m30005004,4 > TX: 00000000 > RX: vCont;s That's a step request. > TX: T0b01:7ffffa60;40:1000056c; That's a segfault. Your kernel has failed to implement PTRACE_SINGLESTEP correctly. This is a common problem on older 4xx kernels. -- Daniel Jacobowitz