Re: [PATCH 2/2] gdb.threads/attach-into-signal.exp: don't rely on linux native target's internal debug output

[Edjunior Barbosa Machado <emachado at linux dot vnet dot ibm dot com>]

On 02/17/2012 05:37 PM, Pedro Alves wrote:

> The test runs twice, with two variants: once non-threaded, and once
> threaded.  SIGLARM defaults to noprint, but if we set it to print,
> then for the non-threaded case, when we attach and find the main
> thread stopping with SIGLARM, we'll see "Program received signal
> SIGLARM".  For the threaded case, the signal is seen on the non main
> thread, so we won't see "Program received signal SIGLARM".  Instead,
> we check the second thread's siginfo.si_signo.  We can't use this
> method for the non-threaded case too, because the Linux native target
> when attaching finds another signal other than SIGSTOP, puts that
> other signal pending, and waits for the SIGSTOP, so siginfo.si_signo
> will always show SIGSTOP.


It looks like the $_siginfo inspection used in the threaded case is not supported on some architectures (like ppc32 and ppc64, where the testcase returns about 100 failures). From what I noticed in another testcase, gdb.base/siginfo-obj.exp, signal information is currently available only on arm, x86 and x86_64.

Thanks,
-- 
Edjunior