From: Nick Roberts <nickrob@snap.net.nz>
To: gdb@sourceware.org
Subject: Re: PATCH: PR tui/2173: Arrow keys no longer works in breakpoint command list
Date: Sun, 03 Jun 2007 22:54:00 -0000 [thread overview]
Message-ID: <18019.18081.448928.93993@kahikatea.snap.net.nz> (raw)
This change breaks the behaviour of annotations with commands that span
multiple lines, like if, while, etc:
2007-01-03 Jan Kratochvil <jan.kratochvil@redhat.com>
Daniel Jacobowitz <dan@codesourcery.com>
* Makefile.in (top.o): Update.
* top.c (gdb_readline_wrapper_done, gdb_readline_wrapper_result)
(saved_after_char_processing_hook, gdb_readline_wrapper_line)
(struct gdb_readline_wrapper_cleanup, gdb_readline_wrapper_cleanup):
New.
(gdb_readline_wrapper): Rewrite to use asynchronous readline.
To see this compare the output of GDB in CVS with that of 6.6 for the simple
construct:
(gdb) if
>end
(gdb)
With 6.6, omitting ^Z^Z, (gdb -ann=3):
pre-prompt
(gdb)
prompt
if 1
post-prompt
pre-commands
>
commands
end
post-commands
pre-prompt
(gdb)
prompt
With GDB in CVS:
pre-prompt
(gdb)
prompt
if 1
post-prompt
pre-commands
pre-prompt
>
commands
prompt
end
pre-prompt
>
commands
prompt
post-commands
pre-prompt
(gdb)
prompt
where superfluous pre-prompt,prompt and commands annotations are output
(and an extra ">").
--
Nick http://www.inet.net.nz/~nickrob
next reply other threads:[~2007-06-03 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 22:54 Nick Roberts [this message]
2007-06-03 23:10 ` Andreas Schwab
2007-06-03 23:13 ` Andreas Schwab
2007-06-04 1:06 ` Daniel Jacobowitz
2007-06-04 2:09 ` Nick Roberts
2007-06-09 19:29 ` Jan Kratochvil
2007-06-10 1:02 ` Asynchronous Gdb [was Re: PATCH: PR tui/2173: Arrow keys no longer works in breakpoint command list] Nick Roberts
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=18019.18081.448928.93993@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--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