public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Improve the find_nearest_line function for the MIPS target so that it tries harder to find a function name.
Date: Tue, 06 Feb 2018 17:17:00 -0000 [thread overview]
Message-ID: <46d09186d340407fdcf066fea25444682e989512@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 46d09186d340407fdcf066fea25444682e989512 ***
Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 46d09186d340407fdcf066fea25444682e989512
Improve the find_nearest_line function for the MIPS target so that it tries harder to find a function name.
PR 22789
* elfxx-mips.c (_bfd_mips_elf_find_nearest_line): If the dwarf
functions failed to find the function name, try the generic elf
find function instead.
next reply other threads:[~2018-02-06 17:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 17:17 sergiodj+buildbot [this message]
2018-02-06 17:17 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-02-06 18:16 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-02-06 18:33 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-02-06 18:42 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-02-06 18:58 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-06 19:00 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-02-06 19:11 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-02-06 23:40 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-07 0:12 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-02-07 0:59 ` Failures on Ubuntu-AArch32-m32, " 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=46d09186d340407fdcf066fea25444682e989512@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--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).