This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] examine for TYPE_CODE_REF (PR 11349)
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Pierre Muller <pierre dot muller at ics-cnrs dot unistra dot fr>
- Cc: 'Tom Tromey' <tromey at redhat dot com>, gdb-patches at sourceware dot org
- Date: Tue, 4 May 2010 07:22:42 -0700
- Subject: Re: [RFA] examine for TYPE_CODE_REF (PR 11349)
- References: <17731.9300863475$1272644394@news.gmane.org> <m3y6g4zxkr.fsf@fleche.redhat.com> <000c01caea4b$4ef18ba0$ecd4a2e0$@muller@ics-cnrs.unistra.fr> <m3fx28riiy.fsf@fleche.redhat.com> <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