This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: gdb/34
- To: nobody at sources dot redhat dot com
- Subject: Re: gdb/34
- From: Michael Elizabeth Chastain <chastain at cygnus dot com>
- Date: 12 Mar 2001 20:28:00 -0000
- Cc: gdb-prs at sources dot redhat dot com,
- Reply-To: Michael Elizabeth Chastain <chastain at cygnus dot com>
The following reply was made to PR gdb/34; it has been noted by GNATS.
From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: gdb-gnats@sources.redhat.com
Cc:
Subject: Re: gdb/34
Date: Mon, 12 Mar 2001 12:19:04 -0800
There's an explicit test in gdb.c++/method.exp that matches this
bug pretty well.
send_gdb "continue\n"
gdb_expect {
-re "Continuing\\.\r\n\r\nBreakpoint \[0-9\]*, A::foo \\(this=$hex, arg=13\\) at .*method\\.cc:38\r\n38\[\t \]*x \\+= arg;\r\n$gdb_prompt $" {
pass "continued and got breakpoint in A::foo"
}
-re ".*$gdb_prompt $" { fail "continuing and breaking in A::foo" }
timeout { fail "(timeout) continue" }
}
gdb.log says:
continue^M
Continuing.^M
^M
Breakpoint 2, A::foo(int) (this=0xbffff390, arg=13) at /vittone/fsf/2001-03-09/source/gdb/testsuite/gdb.c++/method.cc:38^M
38 x += arg;^M
(gdb) FAIL: gdb.c++/method.exp: continuing and breaking in A::foo