This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Disable thread specific breakpoints when thread dies
- From: Daniel Jacobowitz <drow at false dot org>
- To: Michael Snyder <msnyder at redhat dot com>
- Cc: Andrew STUBBS <andrew dot stubbs at st dot com>, gdb-patches at sources dot redhat dot com
- Date: Thu, 12 Jan 2006 23:31:26 -0500
- Subject: Re: [PATCH] Disable thread specific breakpoints when thread dies
- References: <43723446.7000903@st.com> <20051113184515.GG3599@nevyn.them.org> <437875B0.4000007@st.com> <20051114155659.GA25717@nevyn.them.org> <437A19DE.6040905@st.com> <437B47A1.4040705@st.com> <20051117034811.GB3057@nevyn.them.org> <437CA66B.9060201@st.com> <43C6825C.9020909@st.com> <43C729FA.2020500@redhat.com>
On Thu, Jan 12, 2006 at 08:18:02PM -0800, Michael Snyder wrote:
> Daniel,
>
> valid_thread_id wouldn't be safe, because thread ids might be re-used.
>
> This implementation looks fine to me...
How is this any better in that case? These thread IDs can't be reused
without all the rest of GDB having the same problem - this is GDB's
internal thread ID, not the inferior PTID (see the valid_thread_id
implementation).
>From Andrew's message it sounds like a missing clear of the thread list
at inferior exit. Which I thought someone had fixed just recently.
--
Daniel Jacobowitz
CodeSourcery