Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: mec.gnu@mindspring.com, drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: [testsuite] Kfail signals.exp failures
Date: Fri, 27 Aug 2004 18:42:00 -0000	[thread overview]
Message-ID: <200408271841.i7RIfplE044778@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <412BC24B.9000304@gnu.org> (message from Andrew Cagney on Tue, 24 Aug 2004 18:33:47 -0400)

   Date: Tue, 24 Aug 2004 18:33:47 -0400
   From: Andrew Cagney <cagney@gnu.org>

   As for a separate signals directory, this code is really testing 
   infrun.c (ya), and makes for some fundamental functionality (should have 
   been fixed working 10+ years ago), so I think still belongs in gdb.base. 
     Besides I've been naming all the files sig*.exp so that they are easy 
   to identify.

   I think its better to reserve new directories for things that are 
   clearly separate -> stabs edge cases, dwarf edge cases, C++ lang stuff, 
   ...  We could too easily end up with a pedantic debate over which 
   directory a test belongs (...) :-)

I agree with Andrew here.


  reply	other threads:[~2004-08-27 18:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-08 23:18 Daniel Jacobowitz
2004-08-09  7:00 ` Michael Chastain
2004-08-09 13:18   ` Daniel Jacobowitz
2004-08-09  7:46 ` Mark Kettenis
2004-08-09 13:11   ` Daniel Jacobowitz
2004-08-09 13:58     ` Andrew Cagney
2004-08-09 15:18       ` Daniel Jacobowitz
2004-08-09 16:17         ` Andrew Cagney
2004-08-09 16:44       ` Michael Chastain
2004-08-24 22:35         ` Andrew Cagney
2004-08-27 18:42           ` Mark Kettenis [this message]
2004-08-09 19:43       ` Andreas Schwab

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=200408271841.i7RIfplE044778@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=cagney@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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