From: Simon Marchi <simon.marchi@ericsson.com>
To: <lgustavo@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3] Introduce remote_target_is_gdbserver
Date: Thu, 11 Sep 2014 19:33:00 -0000 [thread overview]
Message-ID: <5411F8EC.9080804@ericsson.com> (raw)
In-Reply-To: <5411C969.9050107@codesourcery.com>
> Just a thought but... is there a specific reason we need to check for
> gdbserver explicitly as opposed to checking for a remote debugging stub
> feature?
>
> It sounds more appropriate to leave remote stub-based testing as generic
> as possible, in which case "is_gdbserver" wouldn't be needed.
Good point, but I'd rather not address this in the current patch. I don't
want to change the test itself, but just make the check available to other
tests.
Ultimately, I want to use it in this patch [1] where I really want to check
for GDBserver. I want to KFAIL a test only when using gdbserver, due to a
known bug in gdbserver.
[1] https://sourceware.org/ml/gdb-patches/2014-09/msg00148.html
next prev parent reply other threads:[~2014-09-11 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 14:54 Simon Marchi
2014-09-11 15:57 ` Doug Evans
2014-09-11 19:26 ` Simon Marchi
2014-09-11 16:10 ` Luis Machado
2014-09-11 19:33 ` Simon Marchi [this message]
2014-09-11 19:36 ` Luis Machado
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=5411F8EC.9080804@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.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).