[Bug server/18367] New: gdbserver doesn't work if parent blocks SIGCHLD

["MatthewS.Grochowalski at ge dot com" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 18367
           Summary: gdbserver doesn't work if parent blocks SIGCHLD
           Product: gdb
           Version: 7.9
            Status: NEW
          Severity: normal
          Priority: P2
         Component: server
          Assignee: unassigned at sourceware dot org
          Reporter: MatthewS.Grochowalski at ge dot com
  Target Milestone: ---

Steps to reproduce (on Linux x86):
1. Launch gdbserver from a parent that has SIGCHLD blocked. For example,
replace SIGINT with SIGCHLD in the code in
http://stackoverflow.com/questions/4515274
2. Try to connect through a gdb client
3. GDB prints the following and remote debugging doesn't work:
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Bogus trace status reply from target: timeout

Running gdbserver with the "--debug" option produces the following output:
>>>> entering linux_wait_1
linux_wait_1: [Process 3252]
my_waitpid (-1, 0x40000001)
my_waitpid (-1, 0x80000001): status(bffff58c), -1
LWFE: waitpid(-1, ...) returned -1, No child processes
leader_pid=3252, leader_lp!=NULL=1, num_lwps=1, zombie=0
sigsuspend'ing

This was introduced some time after 7.3. Looks like it may be due to the fix
for PR 12702.

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