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] Rework signal frame probing for FreeBSD/x86 Date: Thu, 26 Feb 2015 17:40:00 -0000 [thread overview] Message-ID: <cf424aef0af89903abdd6c4e055684929e4990af@kwanyin> (raw) *** TEST RESULTS FOR COMMIT cf424aef0af89903abdd6c4e055684929e4990af *** Author: John Baldwin <jhb@freebsd.org> Branch: master Commit: cf424aef0af89903abdd6c4e055684929e4990af Rework signal frame probing for FreeBSD/x86 - Use signal frame sniffers that look for the signal trampoline instruction sequence to detect most signal frames. - FreeBSD kernels between 9.2 and 10.1 inclusive do not include the signal trampoline code in process core dumps. To detect signal frames for core dumps under these kernels, use the kern.proc.sigtramp.<pid> sysctl to fetch the location of the signal trampoline in the gdb process and assume that PC values within this location are signal frames. This depends on that location being identical for all binaries. gdb/ChangeLog: 2015-02-25 John Baldwin <jhb@FreeBSD.org> * amd64fbsd-nat.c: Include sys/user.h. (_initialize_amd64fbsd_nat): Use the KERN_PROC_SIGTRAMP sysctl instead of KERN_PS_STRINGS to locate the signal trampoline. * i386fbsd-nat.c: Include sys/user.h. (_initialize_i386fbsd_nat): Use the KERN_PROC_SIGTRAMP sysctl instead of KERN_PS_STRINGS to locate the signal trampoline. * amd64fbsd-tdep.c (amd64fbsd_sigtramp_code): New. (amd64fbsd_sigtramp_p): New. (amd64fbsd_sigtramp_start_addr, amd64fbsd_sigtramp_end_addr): No longer set default values. (amd64fbsd_init_abi): Set "sigtramp_p" to "amd64fbsd_sigtramp_p". * i386fbsd-tdep.c (i386fbsd_sigtramp_start) (i386fbsd_sigtramp_middle, i386fbsd_sigtramp_end) (i386fbsd_freebsd4_sigtramp_start) (i386fbsd_freebsd4_sigtramp_middle) (i386fbsd_freebsd4_sigtramp_end, i386fbsd_osigtramp_start) (i386fbsd_osigtramp_middle, i386fbsd_osigtramp_end): New. (i386fbsd_sigtramp_p): New. (i386fbsd_sigtramp_start_addr, i386fbsd_sigtramp_end_addr): No longer set default values. (i386fbsd_init_abi): Set "sigtramp_p" to "i386fbsd_sigtramp_p".
next reply other threads:[~2015-02-26 16:30 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-26 17:40 sergiodj+buildbot [this message] 2015-02-26 17:46 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, branch master sergiodj+buildbot 2015-02-26 19:56 ` Failures on Fedora-i686, " sergiodj+buildbot 2015-02-26 21:16 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot 2015-02-26 21:40 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot 2015-02-27 4:14 ` Failures on Debian-i686, " sergiodj+buildbot 2015-02-27 5:02 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot 2015-02-27 6:12 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2015-02-27 16:44 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot 2015-02-27 17:05 ` Failures on Debian-x86_64-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=cf424aef0af89903abdd6c4e055684929e4990af@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: 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).