This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: threads/1874: thread-db.c: check_event use of DECR_PC_AFTER_BREAKbreaks thread debugging [AMD64;FC3]
- From: "Philip D.S. Thoren" <pthoren at cs dot uml dot edu>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 19 Feb 2005 20:28:00 -0000
- Subject: Re: threads/1874: thread-db.c: check_event use of DECR_PC_AFTER_BREAKbreaks thread debugging [AMD64;FC3]
- Reply-to: "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: Sat, 19 Feb 2005 15:23:55 -0500
Ok... I should have proof read this. Nevertheless, I hope what I've
found helps fix this problem.
I forgot to add that I did try running gdb with the DECR_PC_AFTER_BREAK
set to 0 and gdb didn't work right.
So, something is potentially affecting the read_pc_pid(ptid) value by 1
between it's detection and when it's passed to check_event in thread-db.c.