public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Use exec_file_find to prepend gdb_sysroot in follow_exec
Date: Tue, 28 Apr 2015 11:34:00 -0000 [thread overview]
Message-ID: <ff862be47e7acf51e4abaf0f121d5961adb1845a@kwanyin> (raw)
*** TEST RESULTS FOR COMMIT ff862be47e7acf51e4abaf0f121d5961adb1845a ***
Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: ff862be47e7acf51e4abaf0f121d5961adb1845a
Use exec_file_find to prepend gdb_sysroot in follow_exec
This commit updates follow_exec to use exec_file_find to prefix
the new executable's filename with gdb_sysroot rather than doing
it longhand.
gdb/ChangeLog:
* infrun.c (solist.h): New include.
(follow_exec): Use exec_file_find to prefix execd_pathname
with gdb_sysroot.
next reply other threads:[~2015-04-28 11:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 11:34 sergiodj+buildbot [this message]
2015-04-28 11:35 ` Failures on Fedora-ppc64be-cc-with-index, branch master sergiodj+buildbot
2015-04-28 11:36 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-04-28 11:38 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2015-04-28 11:40 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2015-04-28 11:41 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-04-28 11:43 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2015-04-28 11:45 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2015-04-28 11:59 ` Failures on Debian-i686, " sergiodj+buildbot
2015-04-28 12:17 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2015-04-28 17:17 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2015-04-28 17:22 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
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=ff862be47e7acf51e4abaf0f121d5961adb1845a@kwanyin \
--to=sergiodj+buildbot@redhat.com \
--cc=gdb-testers@sourceware.org \
/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).