From: Tom Tromey <tromey@redhat.com>
To: GDB Development <gdb@sourceware.org>
Subject: FYI: fix PR 10684
Date: Wed, 23 Sep 2009 17:19:00 -0000 [thread overview]
Message-ID: <m3y6o5mvd7.fsf@fleche.redhat.com> (raw)
I am checking this in on the trunk and the 7.0 branch.
This patch comes from PR 10684. It is small enough not to require
paperwork.
This is an obvious fix to the continued-line logic.
Tom
2009-09-23 John Wright <john.wright@hp.com>
PR gdb/10684:
* event-top.c (command_line_handler): Terminate linebuffer before
xstrdup.
Index: event-top.c
===================================================================
RCS file: /cvs/src/src/gdb/event-top.c,v
retrieving revision 1.68
diff -u -c -r1.68 event-top.c
cvs diff: conflicting specifications of output style
*** event-top.c 23 May 2009 16:17:15 -0000 1.68
--- event-top.c 23 Sep 2009 17:13:26 -0000
***************
*** 622,627 ****
--- 622,628 ----
if (p > linebuffer && *(p - 1) == '\\')
{
+ *p = '\0';
p--; /* Put on top of '\'. */
readline_input_state.linebuffer = xstrdup (linebuffer);
next reply other threads:[~2009-09-23 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 17:19 Tom Tromey [this message]
2009-09-23 17:49 ` 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=m3y6o5mvd7.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@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