This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Should this be on the blocker list for the 7.10 release?
- From: Pedro Alves <palves at redhat dot com>
- To: Simon Marchi <simon dot marchi at ericsson dot com>, Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches <gdb-patches at sourceware dot org>
- Date: Tue, 07 Jul 2015 20:20:46 +0100
- Subject: Re: Should this be on the blocker list for the 7.10 release?
- Authentication-results: sourceware.org; auth=none
- References: <559AE482 dot 1010109 at ericsson dot com> <20150707132459 dot GA16734 at adacore dot com> <559BFBBD dot 4000303 at redhat dot com> <559C14B6 dot 5020800 at redhat dot com> <559C1BFB dot 7070308 at ericsson dot com> <559C1EA9 dot 5090400 at redhat dot com> <559C22D1 dot 7020501 at redhat dot com>
On 07/07/2015 08:04 PM, Pedro Alves wrote:
> ...
> WL: waitpid Thread 0x7ffff7fc2740 (LWP 9513) received Trace/breakpoint trap (stopped)
> WL: Handling extended status 0x03057f
> LHEW: Got clone event from LWP 9513, new child is LWP 9579
> [New Thread 0x7ffff37b8700 (LWP 9579)]
> WL: waitpid Thread 0x7ffff7fc2740 (LWP 9508) received 0 (exited)
> WL: Thread 0x7ffff7fc2740 (LWP 9508) exited.
> ^^^^^^^^
> [Thread 0x7ffff7fc2740 (LWP 9508) exited]
> WL: waitpid Thread 0x7ffff7fc2740 (LWP 9499) received 0 (exited)
> WL: Thread 0x7ffff7fc2740 (LWP 9499) exited.
> [Thread 0x7ffff7fc2740 (LWP 9499) exited]
> RSRL: resuming stopped-resumed LWP Thread 0x7ffff37b8700 (LWP 9579) at 0x3615ef4ce1: step=0
> ...
> (gdb) info inferiors
> Num Description Executable
> 5 process 9508 /home/pedro/bugs/src/test
> ^^^^
> 4 process 9503 /home/pedro/bugs/src/test
> 3 process 9500 /home/pedro/bugs/src/test
> 2 process 9499 /home/pedro/bugs/src/test
> * 1 <null> /home/pedro/bugs/src/test
> (gdb)
> ...
>
> Note the "Thread 0x7ffff7fc2740 (LWP 9508) exited." line.
> That's this in wait_lwp:
>
> /* Check if the thread has exited. */
> if (WIFEXITED (status) || WIFSIGNALED (status))
> {
> thread_dead = 1;
> if (debug_linux_nat)
> fprintf_unfiltered (gdb_stdlog, "WL: %s exited.\n",
> target_pid_to_str (lp->ptid));
> }
> }
>
> This code doesn't understand that an WIFEXITED status
> of the last lwp of the process should be reported as
> process exit. Haven't tried to fix it yet.
This one (on top of the other) fixes this for me. No
testsuite regressions on x86_64 F20.
-----
>From 1290101d792c0e1d8c4e202cd7d900837db0ee84 Mon Sep 17 00:00:00 2001
From: Pedro Alves <palves@redhat.com>
Date: Tue, 7 Jul 2015 19:50:38 +0100
Subject: [PATCH] missing exit event
---
gdb/linux-nat.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/gdb/linux-nat.c b/gdb/linux-nat.c
index ea38ebb..281a270 100644
--- a/gdb/linux-nat.c
+++ b/gdb/linux-nat.c
@@ -2275,6 +2275,20 @@ wait_lwp (struct lwp_info *lp)
/* Check if the thread has exited. */
if (WIFEXITED (status) || WIFSIGNALED (status))
{
+ if (ptid_get_pid (lp->ptid) == ptid_get_lwp (lp->ptid))
+ {
+ if (debug_linux_nat)
+ fprintf_unfiltered (gdb_stdlog, "WL: Process %d exited.\n",
+ ptid_get_pid (lp->ptid));
+
+ /* This is the leader exiting, it means the whole
+ process is gone. Store the status to report to the
+ core. Store it in the lp->waitstatus, because
+ W_EXITCODE(0,0) == 0. */
+ store_waitstatus (&lp->waitstatus, status);
+ return 0;
+ }
+
thread_dead = 1;
if (debug_linux_nat)
fprintf_unfiltered (gdb_stdlog, "WL: %s exited.\n",
--
1.9.3