After updating to current sources today, I have noticed a regression in print-threads.exp which is due to some missing logic in my June 4th patch. The problem is a timing issue (it does not occur for my June 4th build). There is a gdb_assert in thread_from_lwp() which gets triggered because the th_valid flag has not been set for a zombie thread's thread_info struct. This patch fills in the zombie thread's thread_info private area since the information is indeed valid and available. Ok to commit? -- Jeff J. 2004-06-07 Jeff Johnston * thread-db.c (thread_get_info_callback): Fill in the thread_info struct if one exists, even if we are dealing with a zombie thread.