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: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 13 May 2010 16:46:45 -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 dje at google dot com 2010-05-13 16:46 -------
I think one needs to separate the handling of scheduler-locking when the current
target can't handle it from the handling of scheduler-locking on a re-run.
In the re-run case, having scheduler-locking on at the start of program
execution can cause confusion / headaches.
scheduler-locking is a session variable, when often what one wants is to just
enable scheduler-locking temporarily - it's an attribute of the next command,
not the entire session. i.e. maybe instead of scheduler-locking=on we had
tstep, tnext, tcontinue (or continue -t or whatever) that just
step'd/next'd/continue'd/etc. the current thread only.
--
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.