From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Elizabeth Chastain To: chastain@cygnus.com, msnyder@cygnus.com Cc: gdb-patches@sources.redhat.com Subject: Re: [RFA] testsuite/gdb.c++/derivation.exp: use 'runto' library function Date: Mon, 12 Mar 2001 12:17:00 -0000 Message-id: <200103122017.MAA01686@bosch.cygnus.com> X-SW-Source: 2001-03/msg00172.html Michael Snyder writes: > Maybe we should add one, somewhere (if not in this file), > so that that bug cannot slip thru the cracks? 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 I'll add a note to PR gdb/34 that it's tested in gdb.c++/method.exp. Do you want me to add a note to gdb.c++/method.exp that it tests PR gdb/34? Michael