From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3413 invoked by alias); 24 Mar 2004 15:07:47 -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 3406 invoked from network); 24 Mar 2004 15:07:46 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 24 Mar 2004 15:07:46 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1B69ys-0006zt-EX; Wed, 24 Mar 2004 10:07:46 -0500 Date: Wed, 24 Mar 2004 15:44:00 -0000 From: Daniel Jacobowitz To: Lukas Heiniger Cc: gdb@sources.redhat.com Subject: Re: SIGTRAP or SIG32 when remote debugging threads Message-ID: <20040324150746.GA26874@nevyn.them.org> Mail-Followup-To: Lukas Heiniger , gdb@sources.redhat.com References: <200403191107.34202.lukas.heiniger@fela.ch> <200403241411.16660.lukas.heiniger@fela.ch> <20040324143913.GA25841@nevyn.them.org> <200403241603.13624.lukas.heiniger@fela.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200403241603.13624.lukas.heiniger@fela.ch> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-03/txt/msg00235.txt.bz2 On Wed, Mar 24, 2004 at 04:03:13PM +0100, Lukas Heiniger wrote: > On Wednesday 24 March 2004 15:39, Daniel Jacobowitz wrote: > > On Wed, Mar 24, 2004 at 02:11:16PM +0100, Lukas Heiniger wrote: > > > It looks like setting and hitting the shlib event breakpoint works. > > > > Not to me. Is 0x40002570 the shlib event breakpoint, and if so, why > > are you stopped there instead of at the first instruction in the > > program? > > According to 'maint info breakpoints' (you can find it approximately in the > middle of my last session) the shlib event breakpoint is located at > 0x4000c3fc. After entering 'continue', gdb seems to set a breakpoint there. > The instruction is restored after SIG32 has been received. > > I think that 0x40002570 actually is the first instruction in the program. In that case the breakpoint was not hit, just set, according to your log. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer