Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Fix break-probes.exp with native-gdbserver
Date: Thu, 18 Apr 2019 18:13:00 -0000	[thread overview]
Message-ID: <27f28bbf-107d-dbd0-9bbd-480776aa5d0c@redhat.com> (raw)
In-Reply-To: <20190418165011.GA14803@delia>

On 4/18/19 5:50 PM, Tom de Vries wrote:
> Hi,
> 
> When running break-probes.exp with native-gdbserver, we run into:
> ...
> FAIL: gdb.base/break-probes.exp: run til our library loads (the program exited)
> FAIL: gdb.base/break-probes.exp: call (int) foo(23)
> ...
> due to the fact that we're trying to match:
> ...
> Inferior loaded /data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base\
>   /break-probes/break-probes-solib.so
> ...
> using pattern:
> ...
> Inferior loaded $sysroot$binfile_lib
> ...
> which expands into:
> ...
> Inferior loaded //data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base\
>   /break-probes/break-probes-solib.so
> ...
> 
> Fix this by removing trailing slashes from the sysroot variable.
> 
> Tested on x86_64-linux with native and native-gdbserver (with sysroot set to
> "/", "/." and "/./").
> 
> OK for trunk?
> 

I think we made a little mistake in the recent "set sysroot in board file" patch:

commit c92df149c29518f6e1d4a3174b3e29162fcd3ad6
Author:     Alan Hayward <alan.hayward@arm.com>
AuthorDate: Thu Mar 28 12:33:29 2019 +0000

    Testsuite: set sysroot when using gdbserver

I think it would be better to make that do

"set sysroot"

instead of the current

"set sysroot /"

Setting the sysroot to empty means to read from the local filesystem,
which is what was intended.

And with that, this patch shouldn't be necessary.

Thanks,
Pedro Alves


  reply	other threads:[~2019-04-18 18:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 16:50 Tom de Vries
2019-04-18 18:13 ` Pedro Alves [this message]
2019-04-18 21:42   ` Tom de Vries
2019-05-08  2:09     ` Simon Marchi
2019-05-24  7:50       ` Tom de Vries

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=27f28bbf-107d-dbd0-9bbd-480776aa5d0c@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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