From: Daniel Jacobowitz <drow@false.org>
To: suresh ds <dssuresh66@mail.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb@sourceware.org
Subject: Re: Behaviour of default all-stop mode -- Why no one has replied ?
Date: Mon, 15 Jun 2009 16:51:00 -0000 [thread overview]
Message-ID: <20090615165102.GA15784@caradoc.them.org> (raw)
In-Reply-To: <20090615153658.A0684606884@ws1-4.us4.outblaze.com>
On Mon, Jun 15, 2009 at 10:36:58AM -0500, suresh ds wrote:
> 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 ?
I don't know, but you may want to investigate the scheduler-locking
setting. Also, don't be fooled by GDB's behavior when there is a
breakpoint at the current address; that's a special case that trips up
a lot of people. Look at the following vCont after GDB has navigated
off the breakpoint.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-06-15 16:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 15:37 suresh ds
2009-06-15 16:51 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-20 10:50 suresh ds
2009-07-21 14:00 ` Pedro Alves
2009-07-06 14:42 suresh ds
2009-07-06 17:03 ` Pedro Alves
2009-06-15 15:10 suresh ds
2009-06-15 15:20 ` Daniel Jacobowitz
2009-06-15 18:44 ` Pedro Alves
2009-06-15 10:38 suresh ds
2009-06-15 11:01 ` Pedro Alves
2009-06-10 7:18 suresh ds
2009-06-10 17:55 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090615165102.GA15784@caradoc.them.org \
--to=drow@false.org \
--cc=dssuresh66@mail.com \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox