FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Expose current 'print' settings to Python

Browse source 
PR python/17291 asks for access to the current print options.  While I
think this need is largely satisfied by the existence of
Value.format_string, it seemed to me that a bit more could be done.

First, while Value.format_string uses the user's settings, it does not
react to temporary settings such as "print/x".  This patch changes
this.

Second, there is no good way to examine the current settings (in
particular the temporary ones in effect for just a single "print").
This patch adds this as well.

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=17291
This commit is contained in:
Tom Tromey 2022-06-06 09:54:45 -06:00
parent aa63b0a77e
commit c4a3dbaf11
10 changed files with 209 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

4
gdb/python/py-value.c
View file

@ -673,7 +673,7 @@ valpy_format_string (PyObject *self, PyObject *args, PyObject *kw)
}
struct value_print_options opts;
get_user_print_options (&opts);
gdbpy_get_print_options (&opts);
opts.deref_ref = 0;
/* We need objects for booleans as the "p" flag for bools is new in
@ -1163,7 +1163,7 @@ valpy_str (PyObject *self)
{
struct value_print_options opts;
get_user_print_options (&opts);
gdbpy_get_print_options (&opts);
opts.deref_ref = 0;
string_file stb;