Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v4 0/3] Fix failure to detach if process exits while detaching on Linux
Date: Thu, 16 Jun 2016 23:33:00 -0000	[thread overview]
Message-ID: <1466119968-15171-1-git-send-email-palves@redhat.com> (raw)

This series picks up where
 https://sourceware.org/ml/gdb-patches/2016-06/msg00068.html
left off.

New in v4:

 - Handles failure to remove watchpoints / (prepare to resume).

 - Reworked to reap zombie lwps on failure to detach.  Without this,
   gdb actually remains attached to the process.  This can result in
   the process's parent hanging, if it is waiting for the child to
   exit.
   
 - Tests much extended.

 - Commit log tweaked / extended.

Also pushed to users/palves/detach-gone-thread-v4, for convenience.

( Antoine, I rewrote the test substantially, and renamed it to
process-dies-while-detaching.exp to mirror
process-dies-while-handling-bp.exp, which is somewhat similar in
spirit.  You can easily see the differences from what we were working on
earlier with:
git diff -M origin/users/palves/detach-gone-thread-wip..origin/users/palves/detach-gone-thread-v4
)

 gdb/breakpoint.c                                   |  25 +-
 gdb/darwin-nat.c                                   |  10 +-
 gdb/gdbserver/linux-low.c                          | 116 ++++++--
 gdb/inf-ptrace.c                                   |  20 +-
 gdb/inf-ptrace.h                                   |   4 +
 gdb/infcmd.c                                       |   7 +
 gdb/linux-nat.c                                    | 152 ++++++----
 gdb/nto-procfs.c                                   |  11 +-
 gdb/remote.c                                       |  10 +-
 gdb/target.c                                       |  22 ++
 gdb/target.h                                       |   5 +
 gdb/testsuite/gdb.multi/watchpoint-multi-exit.c    |  66 +++++
 gdb/testsuite/gdb.multi/watchpoint-multi-exit.exp  |  87 ++++++
 .../gdb.threads/process-dies-while-detaching.c     | 116 ++++++++
 .../gdb.threads/process-dies-while-detaching.exp   | 327 +++++++++++++++++++++
 15 files changed, 864 insertions(+), 114 deletions(-)
 create mode 100644 gdb/testsuite/gdb.multi/watchpoint-multi-exit.c
 create mode 100644 gdb/testsuite/gdb.multi/watchpoint-multi-exit.exp
 create mode 100644 gdb/testsuite/gdb.threads/process-dies-while-detaching.c
 create mode 100644 gdb/testsuite/gdb.threads/process-dies-while-detaching.exp

-- 
2.5.5


             reply	other threads:[~2016-06-16 23:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16 23:33 Pedro Alves [this message]
2016-06-16 23:32 ` [PATCH v4 1/3] Factor out "Detaching from program" message printing Pedro Alves
2016-06-17 11:31   ` Yao Qi
2016-06-16 23:33 ` [PATCH v4 2/3] Forget watchpoint locations when inferior exits or is killed/detached Pedro Alves
2016-06-17 11:56   ` Yao Qi
2016-06-24 19:10     ` Pedro Alves
2016-07-01 10:49       ` Pedro Alves
2016-06-16 23:33 ` [PATCH v4 3/3] Fix failure to detach if process exits while detaching on Linux Pedro Alves
2016-06-17 13:03   ` Antoine Tremblay
2016-06-24 19:30     ` Pedro Alves
2016-06-17 15:07   ` Yao Qi
2016-06-24 19:28     ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1466119968-15171-1-git-send-email-palves@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox