public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: "Maciej W. Rozycki" <macro@mips.com>, gdb-patches@sourceware.org
Cc: Djordje Todorovic <djordje.todorovic@rt-rk.com>
Subject: Re: [PATCH] testsuite: Extend TLS core file testing with an OS-generated dump
Date: Wed, 23 May 2018 13:35:00 -0000	[thread overview]
Message-ID: <5b76142d-479d-3c34-9294-9f4510d0fc04@redhat.com> (raw)
In-Reply-To: <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

  parent reply	other threads:[~2018-05-23 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23  4:59 Maciej W. Rozycki
2018-05-23  8:50 ` Djordje Todorovic
2018-05-23 13:35 ` Pedro Alves [this message]
2018-05-23 14:17   ` Maciej W. Rozycki
2018-05-23 17:33     ` Pedro Alves
2018-05-23 23:59       ` Maciej W. Rozycki
2018-05-24 15:05         ` Pedro Alves
2018-05-25 13:49           ` Maciej W. Rozycki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5b76142d-479d-3c34-9294-9f4510d0fc04@redhat.com \
    --to=palves@redhat.com \
    --cc=djordje.todorovic@rt-rk.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@mips.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).