[Bug gdb/18364] New: an external SIGCONT can't be ignored and impacts SIGTERM handling

[Bug gdb/18364] New: an external SIGCONT can't be ignored and impacts SIGTERM handling

[P at draigBrady dot com]

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

            Bug ID: 18364
           Summary: an external SIGCONT can't be ignored and impacts
                    SIGTERM handling
           Product: gdb
           Version: 7.9
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: P at draigBrady dot com
  Target Milestone: ---

I see that gdb has specialized SIGCONT and SIGSTOP handling as per
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=9b224c5e
and bug #17024

It's impacting my use case where I'm scripting gdb and wrapping with the
timeout(1) command. The timeout command will send a SIGCONT in case
the command it's monitoring (gdb in this case) is stopped.
I thought I might be able to get gdb to just ignore this signal with
"handle SIGCONT nostop noprint nopass", but even with that
_intermittently_ gdb will fail to stop a running process when it
receives a SIGTERM and SIGCONT. Note when in this state, sending
any signal to the process that gdb is running, will cause that
process to exit and then unlock gdb.

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