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
On Wed, 23 May 2018, Pedro Alves 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?
Possibly. The test case is skipped with all my testing, native or
native-gdbserver, due to the use of `![isnative]' (I have $build !=
$host; the native compiler I have on the host machine is too old to
build GDB these days), so I didn't even notice it there.
> 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.
Acknowledged. Given the current situation I cannot afford investing
any further work into this change, so let's ditch it (and a change to
gdb.base/auxv.exp to use `use_gdb_stub' I planned to submit next). If I
find some time after all, then I can revisit the decision later on.
Maciej