diff options
author | Tankut Baris Aktemur <tankut.baris.aktemur@intel.com> | 2020-12-07 09:20:31 +0100 |
---|---|---|
committer | Tankut Baris Aktemur <tankut.baris.aktemur@intel.com> | 2020-12-07 09:22:06 +0100 |
commit | 5759831a2d06600a7eae4697417a388444c8e13b (patch) | |
tree | c9d0045d36dded7286e2f52b63978d63f162b828 /opcodes/xc16x-desc.h | |
parent | 21e051b3d666bcd614391142a936a8a8cccfa3cb (diff) | |
download | gdb-5759831a2d06600a7eae4697417a388444c8e13b.zip gdb-5759831a2d06600a7eae4697417a388444c8e13b.tar.gz gdb-5759831a2d06600a7eae4697417a388444c8e13b.tar.bz2 |
gdb/linespec: relax the position of the '-force-condition' flag
The break command's "-force-condition" flag is currently required to
be followed by the "if" keyword. This prevents flexibility when using
other keywords, e.g. "thread":
(gdb) break main -force-condition thread 1 if foo
Function "main -force-condition" not defined.
Make breakpoint pending on future shared library load? (y or [n]) n
Remove the requirement that "-force-condition" is always followed by
an "if", so that more flexibility is obtained when positioning
keywords.
gdb/ChangeLog:
2020-12-07 Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
* linespec.c (linespec_lexer_lex_keyword): The "-force-condition"
keyword may be followed by any keyword.
* breakpoint.c (find_condition_and_thread): Advance 'tok' by
'toklen' in the case for "-force-condition".
gdb/testsuite/ChangeLog:
2020-12-07 Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
* gdb.linespec/keywords.exp: Add tests to check positional
flexibility of "-force-condition".
Diffstat (limited to 'opcodes/xc16x-desc.h')
0 files changed, 0 insertions, 0 deletions