This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: SIGTRAP or SIG32 when remote debugging threads

From: Daniel Jacobowitz <drow at false dot org>
To: Lukas Heiniger <lukas dot heiniger at fela dot ch>
Cc: gdb at sources dot redhat dot com
Date: Wed, 24 Mar 2004 09:39:13 -0500
Subject: Re: SIGTRAP or SIG32 when remote debugging threads
References: <200403191107.34202.lukas.heiniger@fela.ch> <200403231755.46001.lukas.heiniger@fela.ch> <20040323191337.GA28050@nevyn.them.org> <200403241411.16660.lukas.heiniger@fela.ch>

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?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Follow-Ups:
- Re: SIGTRAP or SIG32 when remote debugging threads
  - From: Lukas Heiniger

References:
- SIGTRAP or SIG32 when remote debugging threads
  - From: Lukas Heiniger
- Re: SIGTRAP or SIG32 when remote debugging threads
  - From: Lukas Heiniger
- Re: SIGTRAP or SIG32 when remote debugging threads
  - From: Daniel Jacobowitz
- Re: SIGTRAP or SIG32 when remote debugging threads
  - From: Lukas Heiniger

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]