Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Stop sharing .c file between 2 testcases
Date: Fri, 29 Oct 2004 19:43:00 -0000	[thread overview]
Message-ID: <41829CFD.7020009@gnu.org> (raw)
In-Reply-To: <20041029170240.GQ27334@gnat.com>

Joel Brobecker wrote:
> I just read in one thread that we don't want to share .c files between
> testcases. This reminded me of a testcase I recently added which did
> use the .c file from another testcase... This patch should fix it.
> 
> 2004-10-29  Joel Brobecker  <brobecker@gnat.com>
> 
>         * gdb.threads/bp_in_thread.c: New file, copied from
>         pthread_cond_wait.c.
>         * gdb.threads/bp_in_thread.c: Use bp_in_thread.c as the source
>         file, rather than using the .c file of another testcase.
> 
> Tested on x86-linux. Ok to apply?

Right, "obvious".  Good catch.

Andrew


  reply	other threads:[~2004-10-29 19:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29 17:02 Joel Brobecker
2004-10-29 19:43 ` Andrew Cagney [this message]
2004-10-29 21:35   ` Joel Brobecker

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=41829CFD.7020009@gnu.org \
    --to=cagney@gnu.org \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@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