Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Manoj Iyer <manjo@austin.ibm.com>
To: gdb@sources.redhat.com
Subject: testcase help
Date: Wed, 04 Aug 2004 20:45:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0408041458020.17537@lazy> (raw)


I am writing a testcase for gdb in which I want to make GDB continue to
the next breakpoint, so I used gdb_continue "FUNC" to get to the
next breakpoint.

Here is the problem that I have ...

============ testcase code ================
gdb_continue "tf"
gdb_expect {
    -re "Breakpoint .* at .*\r\n$gdb_prompt $" {
        pass "continue to tf";
    }
    -re ".*$gdb_prompt $" {
        fail "continue to tf";
        gdb_suppress_tests;
    }
    timeout {
        fail "continue to tf (timeout)";
        gdb_suppress_tests;
    }
}

=========== Out put ==============
continue
30          for (n = 0; n < N; ++n)
(gdb) FAIL: gdb.threads/thread_break.exp: continue to tf
continue
Continuing.
[New Thread 32769 (LWP 29005)]
[New Thread 16386 (LWP 29006)]
[Switching to Thread 16386 (LWP 29006)]

Breakpoint 2, tf (arg=0x0) at gdb.threads/tbug.c:14
14          int n = (int) (long int) arg;
(gdb) PASS: gdb.threads/thread_break.exp: continue to tf

but a gdb_expect with correct parameters catches this continue as success.
I cannot get it to continue correctly with send_gdb "continue" that is why
I used gdb_continue.

What am I doing wrong?

Thanks
----- ----
Manoj Iyer
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Cognito ergo sum                                                          +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


             reply	other threads:[~2004-08-04 20:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04 20:45 Manoj Iyer [this message]
2004-08-04 22:44 ` Michael Chastain
2004-08-05 15:35   ` Manoj Iyer
2004-08-05 23:26     ` thread testcase compile issue (question) Manoj Iyer
2004-08-06  6:09       ` Michael Chastain

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=Pine.LNX.4.58.0408041458020.17537@lazy \
    --to=manjo@austin.ibm.com \
    --cc=gdb@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