From: Anton Blanchard <anton@samba.org>
To: gdb-patches@sourceware.org, eliz@gnu.org
Subject: [PATCH] TUI: Fix buffer overflow in tui_expand_tabs
Date: Mon, 16 Mar 2015 23:30:00 -0000 [thread overview]
Message-ID: <20150317103009.538f2b3d@kryten> (raw)
tui_expand_tabs writes past the end of the buffers it allocates
because we forget to zero out col. This results in us adding more
spaces than we need to get aligned, and we write past the end of the
allocated buffer.
This was noticed on Ubuntu Vivid ppc64le, where gdb would SEGV when
using the TUI.
2015-03-17 Anton Blanchard <anton@samba.org>
gdb/ChangeLog:
* tui/tui-io.c (tui_expand_tabs): Zero col before reusing.
---
gdb/ChangeLog | 4 ++++
gdb/tui/tui-io.c | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index d984565..4e0177a 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2015-03-17 Anton Blanchard <anton@samba.org>
+
+ * tui/tui-io.c (tui_expand_tabs): Zero col before reusing.
+
2015-03-16 John Baldwin <jhb@FreeBSD.org>
* fbsd-tdep.c (fbsd_make_corefile_notes): Fetch all target registers
diff --git a/gdb/tui/tui-io.c b/gdb/tui/tui-io.c
index a8af9b6..02ae17d 100644
--- a/gdb/tui/tui-io.c
+++ b/gdb/tui/tui-io.c
@@ -690,7 +690,7 @@ tui_expand_tabs (const char *string, int col)
ret = q = xmalloc (strlen (string) + n_adjust + 1);
/* 2. Copy the original string while replacing TABs with spaces. */
- for (s = string; s; )
+ for (col = 0, s = string; s; )
{
char *s1 = strpbrk (s, "\t");
if (s1)
--
2.1.0
next reply other threads:[~2015-03-16 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 23:30 Anton Blanchard [this message]
2015-03-19 21:44 ` Anton Blanchard
2015-03-19 22:58 ` Doug Evans
2015-03-20 8:03 ` Eli Zaretskii
2015-03-20 16:24 ` Doug Evans
2015-03-21 8:53 ` Eli Zaretskii
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=20150317103009.538f2b3d@kryten \
--to=anton@samba.org \
--cc=eliz@gnu.org \
--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