diff options
| author | Mark Kettenis <kettenis@gnu.org> | 2001-03-30 19:36:35 +0000 |
|---|---|---|
| committer | Mark Kettenis <kettenis@gnu.org> | 2001-03-30 19:36:35 +0000 |
| commit | 6b9aa0c1adaefdd9a212b2982da55c3f2b2a4111 (patch) | |
| tree | 2ea1fd2c7f6b374f687e8a1e14a59da8b67e04ff /gdb/thread-db.c | |
| parent | 19598ae2325ececcc134ed1263026a23797337b5 (diff) | |
| download | gdb-6b9aa0c1adaefdd9a212b2982da55c3f2b2a4111.tar.gz | |
* 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.
Diffstat (limited to 'gdb/thread-db.c')
| -rw-r--r-- | gdb/thread-db.c | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/gdb/thread-db.c b/gdb/thread-db.c index 70283d07963..956d0d813b7 100644 --- 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: |