Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <chastain@cygnus.com>
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	[thread overview]
Message-ID: <200103122017.MAA01686@bosch.cygnus.com> (raw)

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


             reply	other threads:[~2001-03-12 12:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-12 12:17 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-12  2:05 Michael Elizabeth Chastain
2001-03-12 11:52 ` Michael Snyder

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=200103122017.MAA01686@bosch.cygnus.com \
    --to=chastain@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@cygnus.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