[RFA,10/10] Call wrap_hint in one more spot in py-framefilter.c
Commit Message
PR python/16486 notes that "bt" output is still wrapped differently
when a frame filter is in use. This patch brings it a bit closer by
adding one more wrap_hint call, in a place where stack.c does this as
well.
ChangeLog
2017-04-25 Tom Tromey <tom@tromey.com>
PR python/16486:
* python/py-framefilter.c (py_print_args): Call wrap_hint.
---
gdb/ChangeLog | 5 +++++
gdb/python/py-framefilter.c | 1 +
2 files changed, 6 insertions(+)
Comments
On 25/04/17 20:41, Tom Tromey wrote:
> PR python/16486 notes that "bt" output is still wrapped differently
> when a frame filter is in use. This patch brings it a bit closer by
> adding one more wrap_hint call, in a place where stack.c does this as
> well.
>
> ChangeLog
> 2017-04-25 Tom Tromey <tom@tromey.com>
>
> PR python/16486:
> * python/py-framefilter.c (py_print_args): Call wrap_hint.
Thanks for catching this. LGTM
Cheers
Phil
On 04/28/2017 04:09 PM, Phil Muldoon wrote:
> On 25/04/17 20:41, Tom Tromey wrote:
>> PR python/16486 notes that "bt" output is still wrapped differently
>> when a frame filter is in use. This patch brings it a bit closer by
>> adding one more wrap_hint call, in a place where stack.c does this as
>> well.
>>
>> ChangeLog
>> 2017-04-25 Tom Tromey <tom@tromey.com>
>>
>> PR python/16486:
>> * python/py-framefilter.c (py_print_args): Call wrap_hint.
>
> Thanks for catching this. LGTM
To me too.
Thanks,
Pedro Alves
@@ -1,5 +1,10 @@
2017-04-25 Tom Tromey <tom@tromey.com>
+ PR python/16486:
+ * python/py-framefilter.c (py_print_args): Call wrap_hint.
+
+2017-04-25 Tom Tromey <tom@tromey.com>
+
* python/py-framefilter.c (py_print_single_arg): Return
EXT_LANG_BT_ERROR from catch.
@@ -864,6 +864,7 @@ py_print_args (PyObject *filter,
TRY
{
+ out->wrap_hint (" ");
annotate_frame_args ();
if (! out->is_mi_like_p ())
out->text (" (");