From: Pedro Alves <pedro@codesourcery.com>
To: "Marc Khouzam" <marc.khouzam@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Allowing all threads of all|current process(es) to be resumed [new command + docs]
Date: Wed, 03 Jun 2009 13:49:00 -0000 [thread overview]
Message-ID: <200906031449.31353.pedro@codesourcery.com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA0784947E@ecamlmw720.eamcs.ericsson.se>
On Monday 01 June 2009 15:28:43, Marc Khouzam wrote:
> Let me ask you, what is the way in non-stop to resume all threads
> of the current process? -exec-continue is for a single thread,
> -exec-continue --all is for all threads of all processes.
Hmm, you must be thinking of something like this? Does it not work?
2008-11-17 Vladimir Prus <vladimir@codesourcery.com>
Implement continue/interrupt of thread groups.
* mi/mi-main.c (proceed_thread_callback): New.
(mi_cmd_exec_continue): If --thread-group is specified, resume all
threads in that group.
(interrupt_thread_callback): New.
(mi_cmd_exec_interrupt): If --thread-group is specified, interrupt
all threads in that group.
> Your proposal addresses this issue for only for all-stop?
Right, all-stop was my main concern. If we always resume
all threads of all inferiors, then even "(gdb) run" to start
up a new process ends up resuming other processes too.
--
Pedro Alves
prev parent reply other threads:[~2009-06-03 13:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 10:51 Pedro Alves
2009-05-30 13:10 ` Eli Zaretskii
2009-05-30 16:01 ` Pedro Alves
2009-05-30 17:12 ` Eli Zaretskii
2009-06-08 11:59 ` Pedro Alves
2009-06-09 4:01 ` Eli Zaretskii
2009-06-11 11:59 ` Pedro Alves
2009-05-31 16:34 ` Doug Evans
2009-05-31 16:40 ` Doug Evans
2009-05-31 18:31 ` Tom Tromey
2009-05-31 18:38 ` Doug Evans
2009-05-31 22:06 ` Pedro Alves
2009-06-01 15:55 ` Doug Evans
2009-06-03 14:06 ` Pedro Alves
2009-06-01 14:29 ` Marc Khouzam
2009-06-03 13:49 ` Pedro Alves [this message]
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=200906031449.31353.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.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