This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug cli/13700] should allow CLI to switch thread on event


http://sourceware.org/bugzilla/show_bug.cgi?id=13700

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |palves at redhat dot com

--- Comment #1 from Pedro Alves <palves at redhat dot com> 2012-02-16 15:13:17 UTC ---
I remembered why I never looked back at this.
It is not clear to me we should always do that.

Consider:

 (gdb) next
 * other random thread stops*
 [switched to $random_thread]
 (gdb) foofoo
 * next finishes later *
 (gdb) foofoofoofoo

I think the user may want to stay focused on the "next" instead of
being distracted by the other stop.

Switching focus on "continue" only would be my next idea, but,
I'm still not sure.  The user may "break foo; continue"; and expect
the foo breakpoint to hit, instead of being distracted by other
threads.

-- 
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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]