diff options
| author | Tom de Vries <tdevries@suse.de> | 2020-03-14 10:41:46 +0100 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2020-03-14 10:41:46 +0100 |
| commit | 2ac70237d2458fb2eb5e73de6bb02a396b5bada0 (patch) | |
| tree | a24ea35968deb3722c51e4dd5c4c83105ce448a5 /gdb/compile/compile-cplus-symbols.c | |
| parent | 09546b56ede31ca2b401e9b03466e8e1fb84d85f (diff) | |
| download | gdb-2ac70237d2458fb2eb5e73de6bb02a396b5bada0.zip gdb-2ac70237d2458fb2eb5e73de6bb02a396b5bada0.tar.gz gdb-2ac70237d2458fb2eb5e73de6bb02a396b5bada0.tar.bz2 | |
[gdb/testsuite] Fix unrecognized debug output level 'statement-frontiers' message
When running testcase gdb.cp/step-and-next-inline.exp, I get:
...
Running src/gdb/testsuite/gdb.cp/step-and-next-inline.exp ...
gdb compile failed, g++: error: unrecognized debug output level \
'statement-frontiers'
gdb compile failed, g++: error: unrecognized debug output level \
'statement-frontiers'
=== gdb Summary ===
# of untested testcases 2
...
Fix this by using a new gdb_caching_proc supports_statement_frontiers.
Tested on x86_64-linux, with gcc 7.5.0 (which does not support
-gstatement-frontiers) and with gcc 8.4.0 (which does support
-gstatement-frontiers).
gdb/testsuite/ChangeLog:
2020-03-14 Tom de Vries <tdevries@suse.de>
* lib/gdb.exp (supports_statement_frontiers): New proc.
* gdb.cp/step-and-next-inline.exp: Use supports_statement_frontiers.
Diffstat (limited to 'gdb/compile/compile-cplus-symbols.c')
0 files changed, 0 insertions, 0 deletions