From: Michael Snyder <msnyder@vmware.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] gdb.threads/*.exp: send_gdb vs. gdb_test
Date: Tue, 01 Jun 2010 22:23:00 -0000 [thread overview]
Message-ID: <4C058858.1070707@vmware.com> (raw)
In-Reply-To: <20100601214837.GS3019@adacore.com>
Joel Brobecker wrote:
>> 2010-05-26 Michael Snyder <msnyder@msnyder-server.eng.vmware.com>
>>
>> * gdb.threads/attach-stopped.exp: Replace send_gdb with gdb_test.
>> * gdb.threads/attachstop-mt.exp: Replace send_gdb with gdb_test.
>> * gdb.threads/gcore-thread.exp: Replace send_gdb with gdb_test.
>> * gdb.threads/hand-call-in-threads.exp: Replace send_gdb with gdb_test.
>> * gdb.threads/linux-dp.exp: Replace send_gdb with gdb_test.
>> * gdb.threads/print-threads.exp: Replace send_gdb with gdb_test.
>> * gdb.threads/pthreads.exp: Replace send_gdb with gdb_test.
>> * gdb.threads/schedlock.exp: Replace send_gdb with gdb_test.
>> * gdb.threads/sigthread.exp: Replace send_gdb with gdb_test.
>
> Looks fine to me. Just one observation...
>
>
>> Index: pthreads.exp
> [...]
>> - send_gdb "continue\n"
>> - gdb_expect {
>> - -re "Continuing.*common_routine.*at.*$srcfile.*$gdb_prompt $" {}
>> + gdb_test_multiple "continue" "continue until common routine run 15 times" {
>> + -re "Continuing.*common_routine.*at.*$srcfile.*$gdb_prompt $" {
>> + }
>> default {
>> fail "continue until common routine run 15 times"
>> return 0
>
> Shouldn't we delete the "default" & "timeout" sections in this case?
I left them in because they do a "return", which wouldn't happen
if they were removed.
next prev parent reply other threads:[~2010-06-01 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 1:24 Michael Snyder
2010-06-01 21:48 ` Joel Brobecker
2010-06-01 22:23 ` Michael Snyder [this message]
2010-06-01 22:49 ` Pedro Alves
2010-06-02 19:59 ` 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=4C058858.1070707@vmware.com \
--to=msnyder@vmware.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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