From: Joel Brobecker <brobecker@adacore.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [resubmit] gdb.base, r*.exp thru w*.exp
Date: Thu, 20 May 2010 21:07:00 -0000 [thread overview]
Message-ID: <20100520210718.GF3019@adacore.com> (raw)
In-Reply-To: <4BF59BBB.8020603@vmware.com>
On Thu, May 20, 2010 at 01:29:47PM -0700, Michael Snyder wrote:
> Incorporating suggestions and changes, including Joel's new function.
>
> 2010-05-20 Michael Snyder <msnyder@vmware.com>
>
> * gdb.base/relational.exp: Replace send_gdb with gdb_test.
> * gdb.base/relocate.exp: Replace send_gdb with gdb_test.
> * gdb.base/return.exp: Replace send_gdb with gdb_test.
> * gdb.base/return2.exp: Replace send_gdb with gdb_test.
> * gdb.base/sepdebug.exp: Replace send_gdb with gdb_test.
> * gdb.base/setvar.exp: Replace send_gdb with gdb_test.
> * gdb.base/shlib-call.exp: Replace send_gdb with gdb_test.
> * gdb.base/shreloc.exp: Replace send_gdb with gdb_test.
> * gdb.base/sigall.exp: Replace send_gdb with gdb_test.
> * gdb.base/sigbpt.exp: Replace send_gdb with gdb_test.
> * gdb.base/signull.exp: Replace send_gdb with gdb_test.
> * gdb.base/so-impl-ld.exp:Replace send_gdb with gdb_test.
> * gdb.base/varargs.exp: Replace send_gdb with gdb_test.
> * gdb.base/volatile.exp: Replace send_gdb with gdb_test.
> * gdb.base/watch_thread_num.exp: Replace send_gdb with gdb_test.
> * gdb.base/watchpoint.exp: Replace send_gdb with gdb_test.
> * gdb.base/whatis.exp: Replace send_gdb with gdb_test.
Looks good overall. It's a long patch, so I only skimmed it.
Just a couple of comments...
> -set name "set catch vfork, never expected to trigger"
> -send_gdb "catch vfork\n"
> -
> # If we are on HP-UX 10.20, we expect an error message to be
> # printed if we type "catch vfork" at the gdb gdb_prompt. This is
> # because on HP-UX 10.20, we cannot catch vfork events.
>
> -if [istarget "hppa*-hp-hpux10.20"] then {
> - gdb_expect {
> - -re "Catch of vfork events not supported on HP-UX 10.20..*$gdb_prompt $"
> - {pass $name}
> - -re "$gdb_prompt $"
> - {fail $name}
> - timeout {fail "(timeout) $name"}
> +set name "set catch vfork, never expected to trigger"
> +gdb_test_multiple "catch vfork" $name {
> + -re "Catch of vfork events not supported on HP-UX 10.20.*" {
> + pass $name
> }
> -} else {
> - gdb_expect {
> - -re "Catchpoint \[0-9\]* .vfork..*$gdb_prompt $"
> - {pass $name}
> - -re "Catch of vfork not yet implemented.*$gdb_prompt $"
> - {pass $name}
> - -re "$gdb_prompt $"
> - {fail $name}
> - timeout {fail "(timeout) $name"}
> + -re "Catchpoint \[0-9\]* .vfork.*$gdb_prompt $" {
> + pass $name
> + }
> + -re "Catch of vfork not yet implemented.*$gdb_prompt $" {
> + pass $name
> }
> }
You slightly changed the implementation, but I think that in practice
this is going to be the same, so I'm OK with that.
> +gdb_test "break 999" "No line 999 in file .*" \
> + pass "break on non-existent source line"
^^^^ ???
> +gdb_test_multiple "break $bp_location1" \
> + "set to-be-silent break bp_location1" {
> + -re "Breakpoint (\[0-9\]*) at .*, line $bp_location1.*$gdb_prompt $" {
> + pass "set to-be-silent break bp_location1"
> + }
How about using test_gdb in this case?
--
Joel
next prev parent reply other threads:[~2010-05-20 21:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 21:01 Michael Snyder
2010-05-20 21:07 ` Joel Brobecker [this message]
2010-05-20 21:14 ` Michael Snyder
2010-05-20 21:28 ` Jan Kratochvil
2010-05-20 21:46 ` Michael Snyder
2010-05-20 21:47 ` Jan Kratochvil
2010-05-20 21:57 ` Michael Snyder
2010-05-20 22:02 ` Jan Kratochvil
2010-05-20 22:07 ` Michael Snyder
2010-05-20 22:07 ` Joel Brobecker
2010-05-20 22:21 ` Michael Snyder
2010-06-15 15:56 ` Frederic Riss
2010-06-15 16:19 ` Daniel Jacobowitz
2010-06-16 8:12 ` Frederic Riss
2010-06-18 0:23 ` Michael Snyder
2010-06-18 7:30 ` Frederic Riss
2010-06-15 17:44 ` 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=20100520210718.GF3019@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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