This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/16768] New: observer mode improvements
- From: "xdje42 at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 28 Mar 2014 18:17:45 +0000
- Subject: [Bug gdb/16768] New: observer mode improvements
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=16768
Bug ID: 16768
Summary: observer mode improvements
Product: gdb
Version: HEAD
Status: NEW
Severity: enhancement
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: xdje42 at gmail dot com
Here are a few suggestions for observer mode improvements.
Observer mode is currently tied to non-stop being on.
Why? [I mean there *could* be a reason, but can we not also have an "observer
mode" for all-stop? There are the may-foo settings, may-write-memory, et.al.
and those can be set in all-stop. So then what does "set observer on" bring to
the table? It's confusing.]
IWBN to be able to switch in and out of observer mode while debugging an
inferior. Currently that doesn't work, at least in part because observer mode
is tied to non-stop mode and one can't currently switch in and out of non-stop
mode while debugging an inferior (while it is running).
ref: https://sourceware.org/bugzilla/show_bug.cgi?id=16767
IWBN if "show observer" (or whatever) showed all the may-foo settings.
Is it too late to deprecate "set may-foo" and have "set may foo" ?
[Then "show may" would solve this.]
Another idea is make "observer" the prefix, still working on how to carry over
the may-foo variables. E.g., "set observer may-insert-breakpoints on" ?
Some users have asked for the ability to tell gdb to not let them alter
inferior state, but still want breakpoints to Just Work.
IWBN to distinguish alteration of inferior state due to things like "set var
foo = 1" vs "b foo ; continue".
IWBN to have a "may-foo" variable that prevents inferior function calls.
set may-hand-call on|off ?
--
You are receiving this mail because:
You are on the CC list for the bug.