Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: gdb.base/auxv.exp: 'untested' instead of gdb_suppress_entire_file
Date: Mon, 02 May 2005 19:14:00 -0000	[thread overview]
Message-ID: <20050502191423.GA16849@nevyn.them.org> (raw)
In-Reply-To: <vt2hdhle95k.fsf@zenia.home>

On Mon, May 02, 2005 at 02:10:31PM -0500, Jim Blandy wrote:
> 
> Looking at this message:
> http://sourceware.org/ml/gdb-patches/2005-04/msg00143.html
> 
> I gather that changes like the below are welcome --- right?
> 
> 2005-05-02  Jim Blandy  <jimb@redhat.com>
> 
> 	* gdb.base/auxv.exp: Call 'untested' and return -1 instead of
> 	calling gdb_suppress_entire_file.

Please, yes.  The results of gdb_suppress_entire_file are so messy!

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-05-02 19:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02 19:13 Jim Blandy
2005-05-02 19:14 ` Daniel Jacobowitz [this message]
2005-05-02 21:00   ` Jim Blandy

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=20050502191423.GA16849@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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