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


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.


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