Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] A new board file remote-gdbserver-on-localhost.exp
Date: Thu, 23 Apr 2015 15:18:00 -0000	[thread overview]
Message-ID: <55390D36.9010200@redhat.com> (raw)
In-Reply-To: <1429796515-26821-1-git-send-email-qiyaoltc@gmail.com>

On 04/23/2015 02:41 PM, Yao Qi wrote:
> From: Yao Qi <yao.qi@linaro.org>
> 
> This patch is to add a new board file that does real remote gdbserver
> testing on localhost.  This board file can be used to reproduce PR 18208.

Awesome.

> +# This gdbserver can only run a process once per session.
> +set_board_info gdb,do_reload_on_run 1
> +
> +# gdbserver does not intercept target file operations and perform them
> +# on the host.
> +set_board_info gdb,nofileio 1
> +
> +# There's no support for argument-passing (yet).
> +set_board_info noargs 1
> +
> +set_board_info exit_is_reliable 1

These two from gdbserver-base.exp seems to be missing:

# The predefined TSVs in GDBserver.
set_board_info gdb,predefined_tsv "\\\$trace_timestamp"

set GDBFLAGS "${GDBFLAGS} -ex \"set auto-connect-native-target off\""

Guess that ideally we'd move the "native" bits out of gdbserver-base.exp
to a native-gdbserver-base.exp file, and make this new one include
gdbserver-base.exp.  (TBC, it's fine with me to push it in without
doing that first).

Thanks,
Pedro Alves


  reply	other threads:[~2015-04-23 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 13:42 Yao Qi
2015-04-23 15:18 ` Pedro Alves [this message]
2015-04-24 10:06   ` Yao Qi
2015-04-24 19:39 ` Sergio Durigan Junior
2015-04-28 10:43   ` Yao Qi
2015-06-22 13:03     ` Yao Qi

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=55390D36.9010200@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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