This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

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

From: Pedro Alves <palves at redhat dot com>
To: Edjunior Barbosa Machado <emachado at linux dot vnet dot ibm dot com>
Cc: gdb-patches at sourceware dot org, jan dot kratochvil at redhat dot com
Date: Tue, 21 Feb 2012 18:54:53 +0000
Subject: Re: [PATCH 2/2] gdb.threads/attach-into-signal.exp: don't rely on linux native target's internal debug output
References: <20120217193546.10029.74207.stgit@hit-nxdomain.opendns.com> <20120217193750.10029.58857.stgit@hit-nxdomain.opendns.com> <4F43DF80.2090701@linux.vnet.ibm.com>

On 02/21/2012 06:16 PM, Edjunior Barbosa Machado wrote:

> 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.

The only reason signal inspection doesn't work on any other GNU/Linux architecture is that
nobody has yet implemented the gdbarch_get_siginfo_type hook for them.  Could this be
enough motivation?  Otherwise we'll have to skip the tests...

-- 
Pedro Alves

References:
- [PATCH 0/2] gdb.threads/attach-into-signal.exp: prepare for gdbserver
  - From: Pedro Alves
- [PATCH 2/2] gdb.threads/attach-into-signal.exp: don't rely on linux native target's internal debug output
  - From: Pedro Alves
- Re: [PATCH 2/2] gdb.threads/attach-into-signal.exp: don't rely on linux native target's internal debug output
  - From: Edjunior Barbosa Machado

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]