diff options
| author | Tom Tromey <tromey@adacore.com> | 2022-06-07 07:05:02 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2022-07-15 09:26:54 -0600 |
| commit | 72be9d6be7de305b34ac298f1466167b9aba9bc2 (patch) | |
| tree | 44543f544c27b7d0006baa6559e72e2d49f4eba0 /gdb/testsuite/gdb.python/py-format-string.exp | |
| parent | c4a3dbaf1132105586586617a59d0e7566eefd41 (diff) | |
| download | binutils-72be9d6be7de305b34ac298f1466167b9aba9bc2.zip binutils-72be9d6be7de305b34ac298f1466167b9aba9bc2.tar.gz binutils-72be9d6be7de305b34ac298f1466167b9aba9bc2.tar.bz2 | |
Add 'summary' mode to Value.format_string
This adds a 'summary' mode to Value.format_string and to
gdb.print_options. For the former, it lets Python code format values
using this mode. For the latter, it lets a printer potentially detect
if it is being called in a backtrace with 'set print frame-arguments'
set to 'scalars'.
I considered adding a new mode here to let a pretty-printer see
whether it was being called in a 'backtrace' context at all, but I'm
not sure if this is really desirable.
Diffstat (limited to 'gdb/testsuite/gdb.python/py-format-string.exp')
| -rw-r--r-- | gdb/testsuite/gdb.python/py-format-string.exp | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.python/py-format-string.exp b/gdb/testsuite/gdb.python/py-format-string.exp index 58bbe85..c432de9 100644 --- a/gdb/testsuite/gdb.python/py-format-string.exp +++ b/gdb/testsuite/gdb.python/py-format-string.exp @@ -1127,6 +1127,12 @@ proc test_print_options {} { "print in binary to fetch options" gdb_test "python print(saved_options\['format'\] == 't')" "True" \ "format was set" + + check_format_string "a_point_t" "summary=True" \ + "No Data" \ + "print in summary mode" + gdb_test "python print(saved_options\['summary'\])" "True" \ + "summary was set" } # Run all the tests in common for both C and C++. |