From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: PR tui/2173: Arrow keys no longer works in breakpoint command list
Date: Tue, 05 Jun 2007 12:56:00 -0000 [thread overview]
Message-ID: <18021.23899.394336.980207@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20070604010633.GA927@caradoc.them.org>
> > This change breaks the behaviour of annotations with commands that span
> > multiple lines, like if, while, etc:
>
> Sorry, I didn't even know we had special annotations for this (and the
> testsuite must not cover it)...
Here's a test for gdb.base/annota3.exp. I can do the same for
gdb.base/annota1.exp and gdb.cp/annota3.exp, if needed.
--
Nick http://www.inet.net.nz/~nickrob
2007-06-06 Nick Roberts <nickrob@snap.net.nz>
* gdb.base/annota3.exp: Test for if construct.
*** annota3.exp 10 Jan 2007 06:59:09 +1300 1.12
--- annota3.exp 06 Jun 2007 00:50:22 +1200
*************** gdb_expect_list "annotation set at level
*** 99,105 ****
"set annotate 3"
}
!
#
# info break:
#
--- 99,121 ----
"set annotate 3"
}
! #
! # if construct:
! #
! send_gdb "if 1\n"
! gdb_expect {
! -re "\r\n\032\032post-prompt\r\n\r\n\032\032pre-commands\r\n >\r\n\032\032commands\r\n" {
! pass "start if construct"
! }
! timeout { fail "start if construct (timeout)" }
! }
! send_gdb "end\n"
! gdb_expect {
! -re "\r\n\032\032post-commands\r\n$gdb_prompt$" {
! pass "end if construct"
! }
! timeout { fail "end if construct (timeout)" }
! }
#
# info break:
#
next parent reply other threads:[~2007-06-05 12:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18019.18081.448928.93993@kahikatea.snap.net.nz>
[not found] ` <20070604010633.GA927@caradoc.them.org>
2007-06-05 12:56 ` Nick Roberts [this message]
2007-06-05 13:27 ` Daniel Jacobowitz
2007-06-24 15:46 ` Daniel Jacobowitz
2007-06-24 21:55 ` Nick Roberts
2007-07-01 22:38 ` Daniel Jacobowitz
2007-07-03 1:28 ` Nick Roberts
2007-07-03 3:03 ` Daniel Jacobowitz
2007-07-03 15:39 ` Daniel Jacobowitz
2007-06-26 13:49 ` Jan Kratochvil
2007-06-26 14:33 ` Daniel Jacobowitz
2008-03-21 20:34 ` Jan Kratochvil
2008-03-21 21:22 ` Daniel Jacobowitz
2008-03-21 21:26 ` Jan Kratochvil
2008-03-21 21:41 ` Daniel Jacobowitz
2006-11-21 21:32 H. J. Lu
2006-11-28 16:53 ` Daniel Jacobowitz
2006-11-28 17:09 ` H. J. Lu
2006-11-28 17:15 ` Daniel Jacobowitz
2006-12-02 18:44 ` H. J. Lu
2006-12-02 18:55 ` Daniel Jacobowitz
2006-12-02 18:59 ` Joel Brobecker
2006-12-02 19:17 ` Chet Ramey
2006-12-02 19:09 ` Chet Ramey
2006-12-02 22:15 ` H. J. Lu
2006-12-02 23:06 ` Daniel Jacobowitz
2006-12-03 5:25 ` Chet Ramey
2006-12-17 23:46 ` Jan Kratochvil
2006-12-18 20:09 ` Chet Ramey
2006-12-19 23:20 ` Jan Kratochvil
2006-12-26 6:00 ` Jan Kratochvil
2007-01-03 21:46 ` Daniel Jacobowitz
2007-01-03 21:47 ` Daniel Jacobowitz
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=18021.23899.394336.980207@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.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