Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Make gdb.server/solib-list.exp work for remote targets
Date: Fri, 08 Apr 2016 22:33:00 -0000	[thread overview]
Message-ID: <570831A6.7070901@redhat.com> (raw)
In-Reply-To: <1460153899-5185-1-git-send-email-simon.marchi@ericsson.com>

Looks good, though see comments below.  Thanks for doing this.

On 04/08/2016 11:18 PM, Simon Marchi wrote:
 
> gdb/testsuite/ChangeLog:
> 
> 	* gdb.server/solib-list.exp: Allow running with remote targets.

Pedantically, this is really a "why", not a "what".  Should be something
around:

	* gdb.server/solib-list.exp: Remove is_remote check.
	Pass shlib= to gdb_compile.  Don't link shared library with
	-soname.  Call gdb_remote_download instead of gdb_load_shlibs.
	Run binary filename through "readlink -f" on the target.

> @@ -75,8 +74,7 @@ foreach nonstop { 0 1 } { with_test_prefix "non-stop $nonstop" {
>      # Note we pass ${interp_system}, the program gdbserver spawns, as
>      # argument here, instead of using gdb_load, because we don't want
>      # to download the interpreter to the target (it's already there)
> -    # or to the test output directory.

Did you remove this line on purpose?  If so, missing period.  :-)

BTW, I actually meant to extended it to:

 "or to the test output directory, when local testing."

before pushing the previous patch, but forgot.

> -    set res [gdbserver_spawn "${interp_system} ${binfile}"]
> +    set res [gdbserver_spawn "${interp_system} ${remote_binfile}"]
>      set gdbserver_protocol [lindex $res 0]
>      set gdbserver_gdbport [lindex $res 1]

Thanks,
Pedro Alves


  reply	other threads:[~2016-04-08 22:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08 22:18 Simon Marchi
2016-04-08 22:33 ` Pedro Alves [this message]
2016-04-08 22:43   ` Simon Marchi
2016-04-08 22:44     ` Pedro Alves
2016-04-08 22:48       ` Simon Marchi

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=570831A6.7070901@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.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