Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Raoul Gough <RaoulGough@yahoo.co.uk>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add shared object relocation tests
Date: Thu, 05 Jun 2003 09:54:00 -0000	[thread overview]
Message-ID: <uk7c0svbk.fsf@yahoo.co.uk> (raw)
In-Reply-To: <ur86b2pkm.fsf@yahoo.co.uk>

Raoul Gough <RaoulGough@yahoo.co.uk> writes:

> Daniel Jacobowitz <drow@mvista.com> writes:
[snip]
>> Please just use return, not gdb_suppress_entire_file.  In particular,
>> using both causes the _next_ test to fail, I think.
>
> Hmmm.... gdb_suppress_entire_file seems to be the usual response to
> testcase compilation failures, so it would probably make more sense to
> remove the return statement instead. I don't really know what the pros
> and cons are in this case - is there some reason to prefer the return
> option (what about logging the error in that case?)

OK, I managed to mess up CC'ing Daniel with my posting, but he
suggested via email that I use "untested" instead of
gdb_suppress_entire_file. It looks like a suitable example is in
src/gdb/testsuite/gdb.java/jmisc.exp in case anyone else is
interested.

I'm updating shreloc.exp now, and will add the files to CVS later
today, unless somebody objects in the mean time.

-- 
Raoul Gough
"Let there be one measure for wine throughout our kingdom, and one
measure for ale, and one measure for corn" - Magna Carta


      reply	other threads:[~2003-06-05  9:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 10:14 Raoul Gough
2003-06-03 13:07 ` Daniel Jacobowitz
2003-06-03 14:39   ` Raoul Gough
2003-06-05  9:54     ` Raoul Gough [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=uk7c0svbk.fsf@yahoo.co.uk \
    --to=raoulgough@yahoo.co.uk \
    --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