From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>,
Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [PATCH] gdb: Don't flush line wrap buffer before adding newline
Date: Tue, 05 Feb 2019 15:10:00 -0000 [thread overview]
Message-ID: <20190205151016.2127-1-andrew.burgess@embecosm.com> (raw)
A bug was introduced in commit:
commit cbe5657196d0d3acbeca39973f93f333ecedacda
Date: Mon Sep 3 22:56:33 2018 -0600
Add output styles to gdb
As GDB produces output, the output is stored in a temporary buffer.
In this way GDB can spot when a line wrap occurs, and can insert a
newline before flushing the contents of the temporary buffer out.
The bug was that the temporary buffer was being flushed out _before_
the newline was added to the output stream, this resulted in incorrect
line wrapping. Here is an example from how GDB announces that a
breakpoint has been hit, first with the bug:
Breakpoint 1, function () at /a/long/pa
th/to/the/source/file.c:123
Now with the bug fixed (this matches the behaviour before the
offending commit):
Breakpoint 1, function ()
at /a/long/path/to/the/source/file.c:123
There are some other issues with line wrapping in current HEAD of GDB,
but these are caused by an unrelated bug.
gdb/ChangeLog:
* utils.c (fputs_maybe_filtered): Don't flush the line wrap buffer
before inserting a newline for line-wrapping.
gdb/testsuite/ChangeLog:
* gdb.base/line-wrapping.c: New file.
* gdb.base/line-wrapping.exp: New file.
---
gdb/ChangeLog | 5 ++++
gdb/testsuite/ChangeLog | 5 ++++
gdb/testsuite/gdb.base/line-wrapping.c | 28 ++++++++++++++++++++++
gdb/testsuite/gdb.base/line-wrapping.exp | 41 ++++++++++++++++++++++++++++++++
gdb/utils.c | 1 -
5 files changed, 79 insertions(+), 1 deletion(-)
create mode 100644 gdb/testsuite/gdb.base/line-wrapping.c
create mode 100644 gdb/testsuite/gdb.base/line-wrapping.exp
diff --git a/gdb/testsuite/gdb.base/line-wrapping.c b/gdb/testsuite/gdb.base/line-wrapping.c
new file mode 100644
index 00000000000..5fdb4462e65
--- /dev/null
+++ b/gdb/testsuite/gdb.base/line-wrapping.c
@@ -0,0 +1,28 @@
+/* This testcase is part of GDB, the GNU debugger.
+
+ Copyright 2019 Free Software Foundation, Inc.
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see <http://www.gnu.org/licenses/>. */
+
+int
+some_rather_long_function_name ()
+{
+ return 0;
+}
+
+int
+main ()
+{
+ return some_rather_long_function_name ();
+}
diff --git a/gdb/testsuite/gdb.base/line-wrapping.exp b/gdb/testsuite/gdb.base/line-wrapping.exp
new file mode 100644
index 00000000000..94b8bc6ea13
--- /dev/null
+++ b/gdb/testsuite/gdb.base/line-wrapping.exp
@@ -0,0 +1,41 @@
+# Copyright 2019 Free Software Foundation, Inc.
+
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+# This tests some line-wrapping cases in GDB.
+
+standard_testfile
+
+if {[prepare_for_testing "failed to prepare" $testfile $srcfile]} {
+ return -1
+}
+
+gdb_test_no_output "set width 55"
+
+if ![runto_main] then {
+ fail "can't run to main"
+ return 0
+}
+
+# Use GDB_TEST here not GDB_CONTINUE_TO_BREAKPOINT as we want to check
+# specifically that the lines are broken at the correct place, and the
+# correct whitespace is added before the "at".
+gdb_breakpoint "some_rather_long_function_name"
+gdb_test "continue" \
+ [multi_line \
+ "Breakpoint 2, some_rather_long_function_name \\(\\)" \
+ " at \[^\r\n\]+$srcfile:$decimal" \
+ "$decimal\[^\r\n\]+"] \
+ "line wrapping at a breakpoint"
+
diff --git a/gdb/utils.c b/gdb/utils.c
index 6fb5736abb5..7bcc4b97b7c 100644
--- a/gdb/utils.c
+++ b/gdb/utils.c
@@ -1788,7 +1788,6 @@ fputs_maybe_filtered (const char *linebuffer, struct ui_file *stream,
if (wrap_column)
{
emit_style_escape (ui_file_style ());
- flush_wrap_buffer (stream);
fputc_unfiltered ('\n', stream);
}
--
2.14.5
next reply other threads:[~2019-02-05 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 15:10 Andrew Burgess [this message]
2019-02-05 15:27 ` Tom Tromey
2019-02-05 15:55 ` Andrew Burgess
2019-02-05 20:44 ` Tom Tromey
2019-02-05 17:15 ` Andrew Burgess
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=20190205151016.2127-1-andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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