Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <lace@jankratochvil.net>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org,
	        Christoph Bartoschek <bartoschek@or.uni-bonn.de>
Subject: Re: RFC: Re: [patch] Fix for 'info threads' crashes if zombie threads exist
Date: Tue, 20 Jun 2006 18:54:00 -0000	[thread overview]
Message-ID: <20060620185326.GA9482@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20060620171109.GA28310@nevyn.them.org>

[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]

Hi Daniel,

On Tue, 20 Jun 2006 19:11:09 +0200, Daniel Jacobowitz wrote:
...
> TD_DEATH events were supported because there are all sorts of things
> which can go wrong when you ask libthread_db about a thread that it
> considers dead.  At that point, as far as the library is concerned, the
> thread is gone.
> After your patch, I strongly suspect there are places where you could hit
> control-c and get mysterious errors from GDB.

OK...  I checked now that my patch may have problems accessing TCB after:
	if (IS_DETACHED (pd)) __free_tcb (pd);
for the detached threads and it even has problems before this point (not
analysed why):
	Program received signal SIGTRAP, Trace/breakpoint trap.
	[Switching to Thread -1208153184 (unknown thread_db state 1)]
	0x00000000 in ?? ()

Proposing the attached reduced patch with only the most important+safe part.
It still catches the initial terminating state with EXITING_BIT
(->TD_THR_ZOMBIE) where I hope most of the crashes/breakpoints may occur.

Still the perfect functionality would require patching libthread_db and it
looks to me a bit as a chicken&egg problem. :-)


> A new thread can be created with the same thread ID - even before this one
> exits.

Not sure of how much are non-Linux platforms a concern for these minor issues.
Apparently on Linux kernel the same LWP id cannot be created until the final
syscall __NR_exit.


Regards,
Jan Kratochvil


> A little patience, please.  It takes a while to review GDB patches,
> especially non-obvious ones - and thread-db support seems to be quite
> complicated.

(Sorry, I only did not want to get the patch lost.)

[-- Attachment #2: gdb-cvs20060620-pthread_exit.patch --]
[-- Type: text/plain, Size: 1415 bytes --]

Index: linux-thread-db.c
===================================================================
RCS file: /cvs/src/src/gdb/linux-thread-db.c,v
retrieving revision 1.16
diff -u -p -r1.16 linux-thread-db.c
--- linux-thread-db.c	5 May 2006 22:42:43 -0000	1.16
+++ linux-thread-db.c	20 Jun 2006 17:51:01 -0000
@@ -1006,6 +1006,9 @@ thread_db_fetch_registers (int regno)
     }
 
   thread_info = find_thread_pid (inferior_ptid);
+  if (!thread_info)
+    error (_("Stopped at dead thread %ld; should not happen."),
+	   (long) GET_THREAD (inferior_ptid));
   thread_db_map_id2thr (thread_info, 1);
 
   err = td_thr_getgregs_p (&thread_info->private->th, gregset);
@@ -1127,6 +1130,8 @@ thread_db_thread_alive (ptid_t ptid)
       struct thread_info *thread_info;
       thread_info = find_thread_pid (ptid);
 
+      if (!thread_info)
+	return 0;
       thread_db_map_id2thr (thread_info, 0);
       if (!thread_info->private->th_valid)
 	return 0;
@@ -1145,9 +1150,9 @@ thread_db_thread_alive (ptid_t ptid)
 	  thread_info->private->ti_valid = 1;
 	}
 
-      if (thread_info->private->ti.ti_state == TD_THR_UNKNOWN
-	  || thread_info->private->ti.ti_state == TD_THR_ZOMBIE)
-	return 0;		/* A zombie thread.  */
+      /* Never 0 on TD_THR_ZOMBIE to be able to trace pthread_exit(3).  */
+      if (thread_info->private->ti.ti_state == TD_THR_UNKNOWN)
+	return 0;		/* A disappeared thread.  */
 
       return 1;
     }

  reply	other threads:[~2006-06-20 18:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200606191719.00530.bartoschek@or.uni-bonn.de>
     [not found] ` <200606201542.12070.bartoschek@or.uni-bonn.de>
     [not found]   ` <20060620135351.GA9853@host0.dyn.jankratochvil.net>
     [not found]     ` <200606201821.41941.bartoschek@or.uni-bonn.de>
     [not found]       ` <200606201456.57681.bartoschek@or.uni-bonn.de>
     [not found]         ` <20060620130932.GA21490@nevyn.them.org>
     [not found]           ` <200606201524.45099.bartoschek@or.uni-bonn.de>
     [not found]             ` <20060620132737.GA21951@nevyn.them.org>
2006-06-19 16:56               ` Jan Kratochvil
2006-06-20 17:05                 ` RFC: " Jan Kratochvil
2006-06-20 17:11                   ` Daniel Jacobowitz
2006-06-20 18:54                     ` Jan Kratochvil [this message]
2006-06-20 19:07                       ` Daniel Jacobowitz
2006-07-13  4:01                         ` Daniel Jacobowitz
2006-07-13 13:28                           ` Jan Kratochvil
2006-07-13 13:43                             ` Daniel Jacobowitz
2006-07-13 15:07                               ` Jan Kratochvil
2006-07-13 18:50                           ` Mark Kettenis
2006-07-13 19:47                             ` Daniel Jacobowitz
2006-07-13 23:16                               ` Mark Kettenis
2006-07-18 22:55                                 ` Daniel Jacobowitz
2006-07-14 13:15                           ` Christoph Bartoschek
2006-07-14 13:36                             ` Daniel Jacobowitz

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=20060620185326.GA9482@host0.dyn.jankratochvil.net \
    --to=lace@jankratochvil.net \
    --cc=bartoschek@or.uni-bonn.de \
    --cc=drow@false.org \
    --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