Re: [PATCH] Fix expected received signal message in testsuite

[Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>]

Ping?  It's been more than a week.

> Quite a number of tests FAIL on Solaris due to a mismatch between
> expected and received messages: the testsuite expects something like
>
> 	Program received signal SIGABRT, Aborted.
>
> while on Solaris it gets
>
> 	Thread 2 received signal SIGABRT, Aborted.
>
> For a simple testcase, info threads shows
>
> (gdb) info threads 
>   Id   Target Id         Frame 
>   1    LWP    1          main () at /vol/src/gnu/gdb/doc/bugs/ua.c:5
> * 2    Thread 1 (LWP 1)  main () at /vol/src/gnu/gdb/doc/bugs/ua.c:5
>
> I suspect this is due to support for the old pre-Solaris 9 MxN thread
> model where user level threads were mapped to a different set of lwps.
>
> For the moment, I'm dealing with this by allowing both forms of the
> message in the testsuite.  The patch is almost completely mechanical,
> with the exception of gdb.base/sigbpt.exp where the introduction of a
> new group in the RE required adjustments in the $expect_out indices.
>
> Tested on sparcv9-sun-solaris2.11, x86_64-pc-solaris2.11, and
> x86_64-pc-linux-gnu.  Ok for master?
>
> 	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University