From: Simon Marchi <simon.marchi@ericsson.com>
To: Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix gdb.threads/dlopen-libpthread.exp crash
Date: Wed, 06 Apr 2016 20:50:00 -0000 [thread overview]
Message-ID: <57057686.9030701@ericsson.com> (raw)
In-Reply-To: <57057506.9070700@redhat.com>
On 16-04-06 04:43 PM, Pedro Alves wrote:
> On 04/06/2016 09:22 PM, Simon Marchi wrote:
>> Following, commit
>>
>> 6e774b13c3b81ac2599812adf058796948ce7e95 Make ftrace tests work with remote targets
>>
>> the test gdb.threads/dlopen-libpthread.exp started to fail with:
>>
>> ERROR: error copying "/home/emaisin/build/binutils-gdb/gdb/testsuite/gdb.threads/dlopen-libpthread.so": no such file or directory
>>
>> This is because the library path is not computed using
>> standard_output_file, so we try to gdb_load_shlibs an unexisting file.
>>
>> gdb/testsuite/ChangeLog:
>>
>> * gdb.threads/dlopen-libpthread.exp: Set binfile_lib using
>> standard_output_file. Remove unused binfile variable.
>
> OK. Thanks!
Pushed, thanks for reporting!
prev parent reply other threads:[~2016-04-06 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 20:22 Simon Marchi
2016-04-06 20:43 ` Pedro Alves
2016-04-06 20:50 ` Simon Marchi [this message]
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=57057686.9030701@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=gdb-patches@sourceware.org \
--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