This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug threads/17067] Cannot send a signal to a thread because the thread is running.
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 18 Jun 2014 16:30:53 +0000
- Subject: [Bug threads/17067] Cannot send a signal to a thread because the thread is running.
- Auto-submitted: auto-generated
- References: <bug-17067-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17067
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--- Comment #1 from Pedro Alves <palves at redhat dot com> ---
You want "interrupt", not "signal".
(gdb) help signal
Continue program with the specified signal.
Usage: signal SIGNAL
The SIGNAL argument is processed the same as the handle command.
An argument of "0" means continue the program without sending it a signal.
This is useful in cases where the program stopped because of a signal,
and you want to resume the program while discarding the signal.
(gdb) help interrupt
Interrupt the execution of the debugged program.
If non-stop mode is enabled, interrupt only the current thread,
otherwise all the threads in the program are stopped. To
interrupt all running threads in non-stop mode, use the -a option.
--
You are receiving this mail because:
You are on the CC list for the bug.