Re: Behaviour of default all-stop mode -- Why no one has replied ?

suresh ds
2009-06-15T15:37:09Z

Thanks Daniel.
I'm still expecting answers for my other queries.
1) When I continue, gdb sends packet only to resume one (current) thread. How to make gdb send packets to resume other threads ?
Even if I 'switch' to other thread, and continue, it still keeps sending packets only to the previously set thread.

2) Through 'Thread apply' or Thread-specific breakpoints' also, I'm not able to make gdb send packets to resume threads.

How to achieve this ?

Thanks,
Suresh

----- Original Message -----
From: "Daniel Jacobowitz"
To: "suresh ds"
Cc: "Pedro Alves" , gdb@sourceware.org
Subject: Re: Behaviour of default all-stop mode -- Why no one has replied ?
Date: Mon, 15 Jun 2009 11:20:10 -0400

On Mon, Jun 15, 2009 at 10:09:44AM -0500, suresh ds wrote:
> Then I switched to thread 1. I really a have a big requirement from
> the gdb developers here. Once I switch to a thread, ideally I expect
> all further commands to apply only to that thread; It makes life
> simple, isn't it ?

This is non-stop mode. You need a GDB that supports non-stop mode for
your processor in order to do this.

GDB 6.8 doesn't support non-stop at all. GDB in CVS doesn't support
non-stop for MIPS yet, I believe.

--
Daniel Jacobowitz
CodeSourcery

--
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com