Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: 'Tom Tromey' <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] examine for TYPE_CODE_REF  (PR 11349)
Date: Tue, 04 May 2010 14:22:00 -0000	[thread overview]
Message-ID: <20100504142242.GF2768@adacore.com> (raw)
In-Reply-To: <001801caeb56$599dd070$0cd97150$@muller@ics-cnrs.unistra.fr>

> It's just that all the other tests around this one
> where also written using gdb_expect, and I simply copy
> and adapted one...

I guessed that this was the case ;-).  But using send_gdb/gdb_expect
is bad, because the gdb_expect block typically does not handle all known
error situations.  That's why we have gdb_test and gdb_test_multiple.
In the future, you can assume that it is required that new test be
written using gdb_test/gdb_test_multiple, even if the tests already
written around the new one still use send_gdb. Conversions of old uses
of send_gdb/gdb_expect will also be very much appreciated.  In fact,
I'll add that to the list of possible projects in the Wiki - it's an
easy task for someone who does not know GDB but wants to contribute :).

-- 
Joel


      reply	other threads:[~2010-05-04 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17731.9300863475$1272644394@news.gmane.org>
2010-04-30 16:59 ` [RFC] examine for TYPE_CODE_REF in pascal language PR 11349 Tom Tromey
2010-05-02 23:01   ` [RFA] examine for TYPE_CODE_REF (PR 11349) Pierre Muller
2010-05-03 17:40     ` Tom Tromey
2010-05-04  6:52       ` Pierre Muller
2010-05-04 14:22         ` Joel Brobecker [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=20100504142242.GF2768@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    --cc=tromey@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