This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] testsuite: Extend TLS core file testing with an OS-generated dump
- From: Pedro Alves <palves at redhat dot com>
- To: "Maciej W. Rozycki" <macro at mips dot com>, gdb-patches at sourceware dot org
- Cc: Djordje Todorovic <djordje dot todorovic at rt-rk dot com>
- Date: Wed, 23 May 2018 13:04:02 +0100
- Subject: Re: [PATCH] testsuite: Extend TLS core file testing with an OS-generated dump
- References: <alpine.DEB.2.00.1805221919470.10896@tp.orcam.me.uk>
On 05/23/2018 12:10 AM, Maciej W. Rozycki wrote:
> to gdbserver testing. The latter is because we'd have to handle core
> file copying from the remote system and then cleaning up with a possibly
> variable name of the core file created. This code has been based on
> gdb.base/auxv.exp, which does not do it either.
Hmm, that sounds like an outdated testcase to copy. See
gdb.threads/corethreads.exp, for example, and the use of the core_find
procedure. Can we use that procedure here too?
I also don't see why (gdbserver && !is_remote) testing can't work, such as
with --target=native-gdbserver and --target=native-extended-gdbserver boards.
It works for gdb.threads/corethreads.exp, for example.
Thanks,
Pedro Alves