This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/12967] event.inferior_thread does not exist inall-stop/sync mode
- From: "tromey at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 31 Jan 2012 16:36:27 +0000
- Subject: [Bug python/12967] event.inferior_thread does not exist inall-stop/sync mode
- Auto-submitted: auto-generated
- References: <bug-12967-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12967
--- Comment #4 from Tom Tromey <tromey at redhat dot com> 2012-01-31 16:36:27 UTC ---
(In reply to comment #3)
> > The docs say that inferior_thread should exist but be None
> > in all-stop. So, I think the bug is that it doesn't exist.
>
> Is there a reason things were done this way? It's awkward that
> the event doesn't say which thread was the event thread in all-stop
> mode. Can't we just change that?
There is a (very mild) compatibility concern.
If that matters then we could do it by adding a new field.
I agree this would be more clean; right now I assume that the
event handler is supposed to know that the current thread is the
stopping thread (if that is even true).
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.