This is the mail archive of the
mailing list for the GDB project.
Re: [RFA/testsuite] Suppress errors building thread tests
- From: Michael Snyder <msnyder at redhat dot com>
- To: Michael Elizabeth Chastain <mec at shout dot net>
- Cc: drow at mvista dot com, gdb-patches at sources dot redhat dot com
- Date: Thu, 02 Jan 2003 11:58:14 -0800
- Subject: Re: [RFA/testsuite] Suppress errors building thread tests
- Organization: Red Hat, Inc.
- References: <200212311902.gBVJ23j24532@duracef.shout.net>
Michael Elizabeth Chastain wrote:
> Recommended for self-approval by Daniel J.
> Proofread and tested. All the pthreads library noise is gone
> from gdb.sum. The results for gcore-thread.exp, print-threads.exp,
> and schedlock.exp are fine.
> > Note the use of gdb_suppress_entire_file. I'm just doing that because it's
> > what the other tests do; I really dislike gdb_suppress_entire_file, so I
> > think I may send along a followup patch to change it to a "return -1".
> > gdb_compile_pthreads already does an "unsupported" if compilation fails. If
> > we can't build the threads tests, there's no point in FAILing them, in my
> > opinion; this clutters up results when I run simulator testing. Thoughts?
> I'm with you. If compilation+linking fails, I am fine with one
> UNSUPPORTED per test script. It would be even better if the UNSUPPORTED's
> come from a known unsupported list rather than dynamic conditions.
> Michael C