From: Daniel Jacobowitz <drow@false.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfa] fix thread_check test
Date: Sun, 28 Nov 2004 17:41:00 -0000 [thread overview]
Message-ID: <20041128174123.GA24639@nevyn.them.org> (raw)
In-Reply-To: <20041123231559.GV9148@tausq.org>
On Tue, Nov 23, 2004 at 03:15:59PM -0800, Randolph Chung wrote:
> i don't think this has ever worked for anybody... :)
>
> The test program name in this test case doesn't match what's in the
> testsuite. The regular expression was wrong as well.
>
> Patch tested on hppa-linux. ok to check in? this should give (almost)
> everbody 2 more PASSes on their testsuite results.
>
> randolph
>
>
> 2004-11-23 Randolph Chung <tausq@debian.org>
>
> testsuite/
>
> * gdb.threads/thread_check.exp: Use $srcfile for test program name
> instead of "tbug". Fix regexp to work properly with gdb_test.
Yes, please check this in.
--
Daniel Jacobowitz
prev parent reply other threads:[~2004-11-28 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 23:16 Randolph Chung
2004-11-28 17:41 ` Daniel Jacobowitz [this message]
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=20041128174123.GA24639@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.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