From: Joel Brobecker <brobecker@adacore.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: runtest gdb testsuite oddities.
Date: Wed, 12 Jan 2011 02:26:00 -0000 [thread overview]
Message-ID: <20110112022548.GB2518@adacore.com> (raw)
In-Reply-To: <m31v4jrosh.fsf@redhat.com>
> Toms check-in today regarding the failure in py-infthread.exp had me
> exploring why I did not see it. For some reason when one runs: runtest
> gdb.python/*.exp the testsuite seems to pass just fine. But when one
> runs just one (failing) exp file, the test fails as it should. I'm not
> sure why, and my fu regarding dejagnu is very slim. Can anyone explain
> what is going on here? Hopefully it is something silly I have done.
Each testcase (.exp) is actually part of the same run. When you think
of scripts being executed, they are actually files being sourced.
So what I am thinking happened to you is that, in your normal context,
you first "ran" (in other words: sourced) a gdb.python testcase that
called "load_lib gdb-python.exp", and thus defined the
gdb_py_test_silent_cmd procedure. "Thanks" to that, by the time dejagnu
"ran" py-infthread.exp, tcl/expect could find gdb_py_test_silent_cmd,
even though the "script" is missing a call to load_lib.
--
Joel
next prev parent reply other threads:[~2011-01-12 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 23:42 Phil Muldoon
2011-01-12 2:26 ` Joel Brobecker [this message]
2011-01-12 12:30 ` Phil Muldoon
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=20110112022548.GB2518@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=pmuldoon@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