From: Jonas Maebe <jonas-devlists@watlock.be>
To: gdb@sourceware.org
Subject: gdb on macOS 10.12 "Sierra"
Date: Sat, 01 Oct 2016 12:08:00 -0000 [thread overview]
Message-ID: <20161001140850.Horde.5Pxfey2wqn5X76dSpncV3uA@mail.elis.ugent.be> (raw)
Hi,
Has anyone succeeded yet in getting gdb to work on macOS 10.12?
Reportedly, it works when you disable SIP (which is understandable,
given
https://developer.apple.com/library/content/documentation/Security/Conceptual/System_Integrity_Protection_Guide/RuntimeProtections/RuntimeProtections.html ), but plain code signing no longer seems to cut
it.
With gdb 7.11.1, I occasionally get this when I try to start an inferior:
During startup program terminated with signal SIG113, Real-time event 113.
and usually (with darwin_debug_flag set to 100 -- didn't manage to get
the SIG113 anymore after I recompiled gdb with that variable set to
100):
***
Starting program: textthr
[632 inferior]: inferior task: 0x300b, pid: 701
[632 inferior]: new_ix:0/1, old_ix:0/0, new_id:0x3203 old_id:0x0
[632 inferior]: darwin_wait: waiting for a message pid=701 thread=0
[701 inferior]: ptrace (PT_TRACE_ME, 0, 0x0, 0): 0 (no error)
[701 inferior]: ptrace (PT_SIGEXC, 0, 0x0, 0): 0 (no error)
message header:
bits: 0x1200
size: 0x24
remote-port: 0x0
local-port: 0xf87
reserved: 0x0
id: 0x48
data: 00000000 00000001 0000300b
[632 inferior]: darwin_wait: pid=701 exit, status=0x5
[632 inferior]: task=0x300b, prev=0x0, notify_port=0xf87
During startup program terminated with signal SIGTRAP, Trace/breakpoint trap.
***
gdb is code signed, the code signing certificate is the System
keychain and set to "Trust always".
Thanks,
Jonas
next reply other threads:[~2016-10-01 12:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 12:08 Jonas Maebe [this message]
2016-10-04 11:42 ` Tristan Gingold
2016-10-04 13:47 ` Tedeschi, Walfred
2016-10-31 11:54 ` Jonas Maebe
2016-10-31 12:00 ` Jack Howarth
2016-10-31 12:11 ` Jonas Maebe
2016-10-31 23:24 ` Jason Molenda
2016-11-03 16:00 ` Tristan Gingold
2016-10-31 23:14 C Western
2016-11-03 22:05 David Jenkins
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=20161001140850.Horde.5Pxfey2wqn5X76dSpncV3uA@mail.elis.ugent.be \
--to=jonas-devlists@watlock.be \
--cc=gdb@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