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] Fetch the ELF auxiliary vector from live processes on FreeBSD. Date: Fri, 24 Jun 2016 19:32:00 -0000 [thread overview] Message-ID: <7697fc9ec3a970f05abb836107653c46ada466ad@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 7697fc9ec3a970f05abb836107653c46ada466ad *** Author: John Baldwin <jhb@FreeBSD.org> Branch: master Commit: 7697fc9ec3a970f05abb836107653c46ada466ad Fetch the ELF auxiliary vector from live processes on FreeBSD. Use the kern.proc.auxv.<pid> sysctl to fetch the ELF auxiliary vector for a live process. gdb/ChangeLog: * fbsd-nat.c [KERN_PROC_AUXV] New variable super_xfer_partial. (fbsd_xfer_partial): New function. (fbsd_nat_add_target) [KERN_PROC_AUXV] Set "to_xfer_partial" to "fbsd_xfer_partial".
next reply other threads:[~2016-06-24 19:32 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-06-24 19:32 sergiodj+buildbot [this message] 2016-06-24 19:38 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot 2016-06-24 20:19 ` Failures on Debian-i686, " sergiodj+buildbot 2016-06-24 20:57 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2016-06-24 21:55 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-06-25 20:37 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2016-06-25 20:38 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-06-26 4:36 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-06-26 4:37 ` Failures on Fedora-ppc64le-native-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=7697fc9ec3a970f05abb836107653c46ada466ad@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: linkBe 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).