tromey at sourceware dot org
2014-11-04 16:12:09 UTC
https://sourceware.org/bugzilla/show_bug.cgi?id=17548
Bug ID: 17548
Summary: turn off RET command-repeat behavior
Product: gdb
Version: 7.7
Status: NEW
Severity: enhancement
Priority: P2
Component: cli
Assignee: unassigned at sourceware dot org
Reporter: tromey at sourceware dot org
In multi-inferior mode, I find I often will
accidentally type a RET. I think this happens
because I am not sure if the prompt is available or
not, and so without thinking I type RET.
If the prompt is available and the last command
was "cont -a" (which in my recent cases it often is),
then I lose control again -- usually requiring redoing
my debug session (since I was stopped at that specific
spot for a reason...)
There's a more general problem here of gdb's non-stop
output being difficult to navigate. However for this
particular problem I'd be happy with just a way to
disable the command-repetition feature.
Bug ID: 17548
Summary: turn off RET command-repeat behavior
Product: gdb
Version: 7.7
Status: NEW
Severity: enhancement
Priority: P2
Component: cli
Assignee: unassigned at sourceware dot org
Reporter: tromey at sourceware dot org
In multi-inferior mode, I find I often will
accidentally type a RET. I think this happens
because I am not sure if the prompt is available or
not, and so without thinking I type RET.
If the prompt is available and the last command
was "cont -a" (which in my recent cases it often is),
then I lose control again -- usually requiring redoing
my debug session (since I was stopped at that specific
spot for a reason...)
There's a more general problem here of gdb's non-stop
output being difficult to navigate. However for this
particular problem I'd be happy with just a way to
disable the command-repetition feature.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are receiving this mail because:
You are on the CC list for the bug.