* thread-db.c (check_event): Don't report an error if we encounter

a thread creation event for a thread that's already in the thread
list, since that may legitemately happen.  Instead only call
attach_thread if it's not already in the thread list.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 62487dd23f59ec446305651f811ddc7c794f82d1..41a4daa7f41fb1dc9828f479008ea6fe766429f3 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,10 @@
+2001-03-30  Mark Kettenis  <kettenis@gnu.org>
+
+       * thread-db.c (check_event): Don't report an error if we encounter
+       a thread creation event for a thread that's already in the thread
+       list, since that may legitemately happen.  Instead only call
+       attach_thread if it's not already in the thread list.
+
 2001-03-28  Andrew Cagney  <ac131313@redhat.com>
 
        * config/pa/xm-hppah.h (malloc): Really delete declaration

diff --git a/gdb/thread-db.c b/gdb/thread-db.c
index 70283d07963335d11990ce6bc744c06fef99bb86..956d0d813b7a733e0dfab27fbfca0900a4debb6c 100644 (file)
--- a/gdb/thread-db.c
+++ b/gdb/thread-db.c
@@ -697,10 +697,11 @@ check_event (int pid)
        error ("Thread creation event doesn't match breakpoint.");
 #endif
 
-      if (in_thread_list (pid))
-       error ("Spurious thread creation event.");
-
-      attach_thread (pid, msg.th_p, &ti, 1);
+      /* We may already know about this thread, for instance when the
+         user has issued the `info threads' command before the SIGTRAP
+         for hitting the thread creation breakpoint was reported.  */
+      if (! in_thread_list (pid))
+       attach_thread (pid, msg.th_p, &ti, 1);
       return;
 
     case TD_DEATH: