public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [RFA 10/10] Call wrap_hint in one more spot in py-framefilter.c
Date: Tue, 25 Apr 2017 19:42:00 -0000	[thread overview]
Message-ID: <20170425194113.17862-11-tom@tromey.com> (raw)
In-Reply-To: <20170425194113.17862-1-tom@tromey.com>

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(+)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index b6c3f40..406b561 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -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.
 
diff --git a/gdb/python/py-framefilter.c b/gdb/python/py-framefilter.c
index 73f2a31..7114030 100644
--- a/gdb/python/py-framefilter.c
+++ b/gdb/python/py-framefilter.c
@@ -864,6 +864,7 @@ py_print_args (PyObject *filter,
 
   TRY
     {
+      out->wrap_hint ("   ");
       annotate_frame_args ();
       if (! out->is_mi_like_p ())
 	out->text (" (");
-- 
2.9.3

  parent reply	other threads:[~2017-04-25 19:41 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 19:41 [RFA 00/10] various frame filter fixes and cleanups Tom Tromey
2017-04-25 19:41 ` [RFA 01/10] Rationalize "backtrace" command line parsing Tom Tromey
2017-04-26 10:33   ` Eli Zaretskii
2017-06-27 16:25   ` Pedro Alves
2017-07-09 22:34     ` Tom Tromey
2017-07-10 16:48       ` Eli Zaretskii
2017-07-14 12:08       ` Pedro Alves
2017-04-25 19:41 ` [RFA 06/10] Allow C-c to work in backtrace in more cases Tom Tromey
2017-04-28 14:55   ` Phil Muldoon
2017-06-27 16:46   ` Pedro Alves
2017-04-25 19:41 ` [RFA 04/10] Remove EXT_LANG_BT_COMPLETED Tom Tromey
2017-04-28 14:52   ` Phil Muldoon
2017-06-27 16:40     ` Pedro Alves
2017-04-25 19:42 ` [RFA 03/10] Allow elision of some filtered frames Tom Tromey
2017-04-26 10:35   ` Eli Zaretskii
2017-04-28 14:50   ` Phil Muldoon
2017-06-27 16:40   ` Pedro Alves
2017-06-27 20:01     ` Tom Tromey
2017-04-25 19:42 ` [RFA 09/10] Return EXT_LANG_BT_ERROR in one more spot in py-framefilter.c Tom Tromey
2017-04-28 15:08   ` Phil Muldoon
2017-06-27 17:31   ` Pedro Alves
2017-06-27 19:08     ` Pedro Alves
2017-04-25 19:42 ` Tom Tromey [this message]
2017-04-28 15:09   ` [RFA 10/10] Call wrap_hint " Phil Muldoon
2017-06-27 17:35     ` Pedro Alves
2017-04-25 19:42 ` [RFA 07/10] Throw a "quit" on a KeyboardException " Tom Tromey
2017-04-28 15:06   ` Phil Muldoon
2017-06-27 16:59   ` Pedro Alves
2017-04-25 19:42 ` [RFA 05/10] Avoid manual resource management " Tom Tromey
2017-04-28 14:53   ` Phil Muldoon
2017-06-27 16:43   ` Pedro Alves
2017-04-25 19:43 ` [RFA 02/10] Change backtrace_command_1 calling to use flags Tom Tromey
2017-04-28 14:40   ` Phil Muldoon
2017-06-27 16:29   ` Pedro Alves
2017-07-09 22:22     ` Tom Tromey
2017-07-14 12:02       ` Pedro Alves
2017-07-14 19:16         ` Tom Tromey
2017-04-25 19:43 ` [RFA 08/10] Move some code later in backtrace_command_1 Tom Tromey
2017-04-28 15:08   ` Phil Muldoon
2017-06-27 17:18   ` Pedro Alves
2017-04-27  8:58 ` [RFA 00/10] various frame filter fixes and cleanups Phil Muldoon
2017-05-29 17:21 ` Tom Tromey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170425194113.17862-11-tom@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).