This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug threads/11580] scheduler-locking breaks re-runs
- From: "pedro at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 12 May 2010 18:04:51 -0000
- Subject: [Bug threads/11580] scheduler-locking breaks re-runs
- References: <20100507183730.11580.k04jg02@gmail.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From pedro at codesourcery dot com 2010-05-12 18:04 -------
Please no special casing like that.
IMO, auto disabling the setting behind the user, or frontend's back
is a bad idea. Better would be to optimistically enable setting
scheduler locking when the target is exec, and instead complain/error
later if the target being resumed doesn't support it.
That is, have the "set scheduler-lock..." command implementation
confirm is it is possible to enable schedlocking on the spot iff
there's execution (target_has_execution), and, have infcmd.c, `proceed', or
`resume' complain is scheduler locking is on, but the current target
doesn't support it.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11580
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.