[Bug gdb/14559] New: The 'interrupt' command does not work if sigwait is in use

[Bug gdb/14559] New: The 'interrupt' command does not work if sigwait is in use

[luto at mit dot edu]

http://sourceware.org/bugzilla/show_bug.cgi?id=14559

             Bug #: 14559
           Summary: The 'interrupt' command does not work if sigwait is in
                    use
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: luto@mit.edu
    Classification: Unclassified


Take a program that uses sigwait (on Linux).  Invoke gdb.  Start the program
with r&, so it's running asynchronously.  Then type 'interrupt'.  It doesn't
work -- sigwait reports SIGINT.  IMO this is a separate gdb bug from the usual
bugs about SIGINT and sigwait not getting along (e.g. bug 9425): the interrupt
command should be directly stopping the program, not sending SIGINT.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug gdb/14559] The 'interrupt' command does not work if sigwait is in use

[jan.kratochvil at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=14559

Jan Kratochvil <jan.kratochvil at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jan.kratochvil at redhat
                   |                            |dot com
         Depends on|                            |9425

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug gdb/14559] The 'interrupt' command does not work if sigwait is in use

[palves at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=14559

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |palves at redhat dot com

--- Comment #1 from Pedro Alves <palves at redhat dot com> 2012-09-11 15:27:36 UTC ---
Could you do a little test for us, and try "interrupt" with non-stop enabled
(set non-stop on)?  That goes through a different path and stops the inferior
with SIGSTOP instead of SIGINT.  Thanks.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug gdb/14559] The 'interrupt' command does not work if sigwait is in use

[luto at mit dot edu]

http://sourceware.org/bugzilla/show_bug.cgi?id=14559

--- Comment #2 from Andy Lutomirski <luto at mit dot edu> 2012-09-11 21:46:16 UTC ---
That works.  interrupt -a also appears to work.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug gdb/14559] The 'interrupt' command does not work if sigwait is in use

[tromey at redhat dot com]

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

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
                 CC|                            |tromey at redhat dot com

--- Comment #3 from Tom Tromey <tromey at redhat dot com> ---
Moved out of waiting state -- seems legit to me.

See also bug #15250.

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

[Bug gdb/14559] The 'interrupt' command does not work if sigwait is in use

[dje at google dot com]

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

dje at google dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dje at google dot com

--- Comment #4 from dje at google dot com ---
(In reply to Andy Lutomirski from comment #2)
> That works.  interrupt -a also appears to work.

Clarification (for my own purposes): This is still a non-stop vs all-stop
distinction.  "interrupt -a" is an error in all-stop mode (though there's a
plan to treat it like a plain "interrupt" in all-stop).

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

[Bug gdb/14559] The 'interrupt' command does not work if sigwait is in use

[crystalrubytails at gmail dot com]

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

Thi Milton <crystalrubytails at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |crystalrubytails at gmail dot com

--- Comment #6 from Thi Milton <crystalrubytails at gmail dot com> ---
(In reply to dje from comment #4)
> (In reply to Andy Lutomirski from comment #2)
> > That works.  interrupt -a also appears to work.
> https://friday-nightfunkin.com
> Clarification (for my own purposes): This is still a non-stop vs all-stop
> distinction.  "interrupt -a" is an error in all-stop mode (though there's a
> plan to treat it like a plain "interrupt" in all-stop).

Is this publicly released?

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