From: Fred Fish <fnf@fred.ninemoons.com>
To: gdb-patches@sources.redhat.com
Cc: fnf@redhat.com
Subject: [RFA] Only need one "maint info breakpoint" test
Date: Sat, 05 Jan 2002 23:15:00 -0000 [thread overview]
Message-ID: <200201060714.g067E9l07719@fred.ninemoons.com> (raw)
We really only need to run the "maint info breakpoints" test once and
optionally accept the "shlib events" variation. Also tweaked the
whitespace for consistency with the other nearby tests.
2002-01-05 Fred Fish <fnf@redhat.com>
* gdb.base/maint.exp: Simplify the "maint info breakpoints" test to
optionally accept the "shlib events" variation.
Index: gdb.base/maint.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/maint.exp,v
retrieving revision 1.9
diff -c -p -r1.9 maint.exp
*** maint.exp 2002/01/05 02:40:47 1.9
--- maint.exp 2002/01/06 07:12:22
*************** gdb_expect {
*** 415,446 ****
send_gdb "maint info breakpoints\n"
gdb_expect {
! -re "Num\[ \t\]+Type\[ \t\]+Disp\[ \t\]+Enb\[ \t\]+Address\[ \t\]+What\r\n1\[ \t\]+breakpoint\[ \t\]+keep\[ \t\]+y\[ \t\]+$hex in main at.*break.c:75\r\n\[ \t\]+breakpoint already hit 1 time\r\n.*$gdb_prompt $"\
! { pass "maint info breakpoints" }
! -re ".*$gdb_prompt $" { fail "maint info breakpoints" }
! timeout { fail "(timeout) maint info breakpoints" }
}
-
- # Try it again, and check for shlib event info. Not supported everywhere.
- if {! ([istarget "hppa*-*-hpux*"]
- || [istarget "*-*-linux*"]
- || [istarget "*-*-solaris*"])} then {
- setup_xfail "*-*-*"
- }
- send_gdb "maint info breakpoints\n"
- gdb_expect {
- -re "Num\[ \t\]+Type\[ \t\]+Disp\[ \t\]+Enb\[ \t\]+Address\[ \t\]+What\r\n1\[ \t\]+breakpoint\[ \t\]+keep\[ \t\]+y\[ \t\]+$hex in main at.*break.c:75\r\n\[ \t\]+breakpoint already hit 1 time\r\n.*$gdb_prompt $"\
- { pass "maint info breakpoints" }
- -re "Num\[ \t\]+Type\[ \t\]+Disp\[ \t\]+Enb\[ \t\]+Address\[ \t\]+What\r\n1\[ \t\]+breakpoint\[ \t\]+keep\[ \t\]+y\[ \t\]+$hex in main at.*break.c:75\r\n\[ \t\]+breakpoint already hit 1 time\r\n-1\[ \t\]+shlib events\[ \t\]+keep\[ \t\]+y\[ \t\]+$hex.*breakpoint already hit.*$gdb_prompt $"\
- { pass "maint info breakpoints: shlib events" }
- -re ".*$gdb_prompt $" {
- fail "maint info breakpoints: shlib events"
- }
- timeout {
- fail "(timeout) maint info breakpoints: shlib events"
- }
- }
-
send_gdb "maint print\n"
gdb_expect {
--- 415,427 ----
send_gdb "maint info breakpoints\n"
gdb_expect {
! -re "Num\[ \t\]+Type\[ \t\]+Disp\[ \t\]+Enb\[ \t\]+Address\[ \t\]+What\r\n1\[ \t\]+breakpoint\[ \t\]+keep\[ \t\]+y\[ \t\]+$hex in main at.*break.c:75\r\n\[ \t\]+breakpoint already hit 1 time\r\n.*$gdb_prompt $"\
! { pass "maint info breakpoints" }
! -re "Num\[ \t\]+Type\[ \t\]+Disp\[ \t\]+Enb\[ \t\]+Address\[ \t\]+What\r\n1\[ \t\]+breakpoint\[ \t\]+keep\[ \t\]+y\[ \t\]+$hex in main at.*break.c:75\r\n\[ \t\]+breakpoint already hit 1 time\r\n-1\[ \t\]+shlib events\[ \t\]+keep\[ \t\]+y\[ \t\]+$hex.*breakpoint already hit.*$gdb_prompt $"\
! { pass "maint info breakpoints (with shlib events)" }
! -re ".*$gdb_prompt $" { fail "maint info breakpoints" }
! timeout { fail "(timeout) maint info breakpoints" }
}
send_gdb "maint print\n"
gdb_expect {
next reply other threads:[~2002-01-06 7:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 23:15 Fred Fish [this message]
2002-01-20 16:12 ` Andrew Cagney
2002-01-21 8:19 ` Fernando Nasser
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=200201060714.g067E9l07719@fred.ninemoons.com \
--to=fnf@fred.ninemoons.com \
--cc=fnf@redhat.com \
--cc=gdb-patches@sources.redhat.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