public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug threads/17067] New: Cannot send a signal to a thread because the thread is running.
@ 2014-06-18 16:09 hi-angel at yandex dot ru
  2014-06-18 16:30 ` [Bug threads/17067] " palves at redhat dot com
  2014-06-18 17:54 ` hi-angel at yandex dot ru
  0 siblings, 2 replies; 3+ messages in thread
From: hi-angel at yandex dot ru @ 2014-06-18 16:09 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=17067

            Bug ID: 17067
           Summary: Cannot send a signal to a thread because the thread is
                    running.
           Product: gdb
           Version: 7.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: threads
          Assignee: unassigned at sourceware dot org
          Reporter: hi-angel at yandex dot ru

I m trying to send a signal to a thread in order to break the one. But I get an
error. Below is how it looks like:
(gdb) thread apply 4 signal SIGTSTP                                             

Thread 4 (Thread 0x7ffff5fd4700 (LWP 5826)):
Cannot execute this command while the selected thread is running.

It is surely should be possible http://linux.die.net/man/3/pthread_kill
Also I should mention that this is very needed feature, because it is the only
way to pause a particular thread -- for unknown reasons the gdb doesn't support
any other path.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug threads/17067] Cannot send a signal to a thread because the thread is running.
  2014-06-18 16:09 [Bug threads/17067] New: Cannot send a signal to a thread because the thread is running hi-angel at yandex dot ru
@ 2014-06-18 16:30 ` palves at redhat dot com
  2014-06-18 17:54 ` hi-angel at yandex dot ru
  1 sibling, 0 replies; 3+ messages in thread
From: palves at redhat dot com @ 2014-06-18 16:30 UTC (permalink / raw)
  To: gdb-prs

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.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug threads/17067] Cannot send a signal to a thread because the thread is running.
  2014-06-18 16:09 [Bug threads/17067] New: Cannot send a signal to a thread because the thread is running hi-angel at yandex dot ru
  2014-06-18 16:30 ` [Bug threads/17067] " palves at redhat dot com
@ 2014-06-18 17:54 ` hi-angel at yandex dot ru
  1 sibling, 0 replies; 3+ messages in thread
From: hi-angel at yandex dot ru @ 2014-06-18 17:54 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=17067

Hi-Angel <hi-angel at yandex dot ru> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from Hi-Angel <hi-angel at yandex dot ru> ---
Pedro Alves thank you very much, I must be blind!

-- 
You are receiving this mail because:
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-06-18 17:54 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-06-18 16:09 [Bug threads/17067] New: Cannot send a signal to a thread because the thread is running hi-angel at yandex dot ru
2014-06-18 16:30 ` [Bug threads/17067] " palves at redhat dot com
2014-06-18 17:54 ` hi-angel at yandex dot ru

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).