From: "Maciej W. Rozycki" <macro@mips.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: Pedro Alves <palves@redhat.com>,
Kevin Buettner <kevinb@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/2] GDB test suite: Add helper for locating core files
Date: Tue, 17 Oct 2017 13:58:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1710171455530.3886@tp.orcam.me.uk> (raw)
In-Reply-To: <m3mv4vfh92.fsf@oc1027705133.ibm.com>
On Fri, 13 Oct 2017, Andreas Arnez wrote:
> >> Exactly, that's why I originally wrote is_remote instead. And I also
> >> wondered why the core dump tests check isnative. Does anyone run the
> >> testsuite on a native remote setup?
> >
> > Well, I had cases where I did that, and offhand I can find two reasons:
> >
> > 1. You want to verify `gdbserver' itself rather than GDB, in which case
> > you may even run it locally (i.e. where the remote target is really
> > `localhost').
>
> This is the native-gdbserver setup, right? In that case the core dump
> tests should work...
Yes and indeed.
> > 2. You want to test a feature (e.g. an extra register set) only your
> > target system has and it is too slow or unequipped to run DejaGNU
> > itself.
>
> ...and in this case they shouldn't. Do you remember whether you saw
> FAILs from corefile.exp and friends?
Nope, sorry. It was a while ago and I only looked for regressions with
whatever I meant to verify and not preexisting failures anyway.
Maciej
next prev parent reply other threads:[~2017-10-17 13:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 18:42 [PATCH 0/2] GDB test suite: Support targets with systemd-coredump Andreas Arnez
2017-09-18 18:43 ` [PATCH 1/2] GDB test suite: Add helper for locating core files Andreas Arnez
2017-10-07 16:45 ` Kevin Buettner
2017-10-09 18:46 ` Andreas Arnez
2017-10-11 8:17 ` Kevin Buettner
2017-10-11 14:53 ` Andreas Arnez
2017-10-12 13:47 ` Pedro Alves
2017-10-12 16:48 ` Pedro Alves
2017-10-17 9:22 ` Pedro Alves
2017-10-12 17:00 ` Andreas Arnez
2017-10-13 9:28 ` Maciej W. Rozycki
2017-10-13 10:56 ` Andreas Arnez
2017-10-17 13:58 ` Maciej W. Rozycki [this message]
2017-10-17 10:06 ` Pedro Alves
2017-10-17 10:01 ` Pedro Alves
2017-10-17 18:21 ` Maciej W. Rozycki
2017-10-18 11:46 ` Pedro Alves
2017-09-18 18:44 ` [PATCH 2/2] GDB test suite: Get core files on targets with systemd-coredump Andreas Arnez
2017-10-17 10:22 ` Pedro Alves
2017-10-17 17:37 ` Andreas Arnez
2017-10-17 18:09 ` Pedro Alves
2017-10-17 18:14 ` Pedro Alves
2017-10-17 18:17 ` Pedro Alves
2017-10-18 15:56 ` Andreas Arnez
2017-10-19 10:48 ` Pedro Alves
2017-10-23 13:41 ` Andreas Arnez
2017-10-23 14:30 ` Pedro Alves
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=alpine.DEB.2.00.1710171455530.3886@tp.orcam.me.uk \
--to=macro@mips.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=palves@redhat.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).