b9a3f8429b
I noticed this inconsistency in the error messages below:
(gdb) print --1
Left operand of assignment is not an lvalue.
(gdb) thread apply 1 print --1
Thread 1 (Thread 0x7ffff7fb6740 (LWP 17805)):
inverted range
The "inverted range" error happens because get_number_trailer returns
0 to indicate error, but number_or_range_parser::get_number is not
checking for that. I tried detected the error there, but that doesn't
work because number_of_range_parser is used in places that _do_ want
to legitimately handle 0. IMO we should fix get_number_trailer's
interface or use something else when we want to parse 0 too.
I've decided to fix it in a different way, similarly to how
number_or_range_parser::finished was changed in commit
|
||
|---|---|---|
| .. | ||
| base.exp | ||
| bkpt-multi-exec.c | ||
| bkpt-multi-exec.exp | ||
| crashme.c | ||
| dummy-frame-restore.c | ||
| dummy-frame-restore.exp | ||
| goodbye.c | ||
| hangout.c | ||
| hello.c | ||
| info-threads.exp | ||
| multi-arch-exec.c | ||
| multi-arch-exec.exp | ||
| multi-arch.exp | ||
| multi-attach.c | ||
| multi-attach.exp | ||
| multi-term-settings.c | ||
| multi-term-settings.exp | ||
| remove-inferiors.c | ||
| remove-inferiors.exp | ||
| tids.c | ||
| tids.exp | ||
| watchpoint-multi-exit.c | ||
| watchpoint-multi-exit.exp | ||
| watchpoint-multi.c | ||
| watchpoint-multi.exp | ||