Re: threads/1874: thread-db.c: check_event use of DECR_PC_AFTER_BREAKbreaks thread debugging [AMD64;FC3]

["Philip D.S. Thoren" <pthoren at cs dot uml dot edu>]

The following reply was made to PR threads/1874; it has been noted by GNATS.

From: "Philip D.S. Thoren" <pthoren@cs.uml.edu>
To: gdb-gnats@sources.redhat.com
Cc:  
Subject: Re: threads/1874: thread-db.c: check_event use of DECR_PC_AFTER_BREAK
 breaks thread debugging [AMD64;FC3]
Date: Sun, 20 Feb 2005 18:04:23 -0500

 "check_event" must be run everytime "thread_db_wait" (in thread-db.c) is 
 called.
 
 I was checking whether gdb would work on my system by commenting out the 
 DECR_PC_AFTER_BREAK in "check_event":
     stop_pc = read_pc_pid (ptid);// - DECR_PC_AFTER_BREAK;
 
 It happened that it wouldn't catch the create/death events and I 
 remembered I was calling "check_event" for every call to "thread_db_wait":
   /*
   if (ourstatus->kind == TARGET_WAITKIND_STOPPED
       && ourstatus->value.sig == TARGET_SIGNAL_TRAP)
     * Check for a thread event.  *
   */
   check_event (ptid);