From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Tom Tromey <tom@tromey.com>,
gdb-patches@sourceware.org, roirand@adacore.com
Subject: Re: [RFC] Make "run" work on macOS 10.13
Date: Thu, 23 Aug 2018 20:04:00 -0000 [thread overview]
Message-ID: <8736v43l6b.fsf@tromey.com> (raw)
In-Reply-To: <d4d3994e73220253b058babb07c995fc@polymtl.ca> (Simon Marchi's message of "Thu, 23 Aug 2018 12:01:24 -0400")
>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
>> {
>> + /* Starting with Sierra, SIP prevents gdb from attaching to the
>> + shell, so users have to disable startup-with-shell. */
>> + scoped_restore save_startup
>> + = make_scoped_restore (&startup_with_shell, 0);
>> +
>> /* Do the hard work. */
>> fork_inferior (exec_file, allargs, env, darwin_ptrace_me,
Simon> I think this part is good. I would suggest printing a
Simon> message/warnings to indicate that we are disabling startup-with-shell
Simon> (only if startup_with_shell is 1 in the first place).
See the bug and also Pedro's comments on Xavier's similar patch --
there are other, probably better, ideas here.
Simon> The unrelocated value of the symbol is 0xf782. That breakpoint is
Simon> used for "set stop-on-solib-events", it seems, so I tried to enable
Simon> that with both of your patches. I got a stop with Xavier's patch and
Simon> none with Tom's, which leads me to think that Xavier's patch gets it
Simon> right. I think you may be using the executable base address, while we
Simon> actually want to use dyld's base address? This is not very clear to
Simon> me yet.
I think we want Xavier's patch and not mine. Mine was more of a stab in
the dark.
Tom
next prev parent reply other threads:[~2018-08-23 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 20:55 Tom Tromey
2018-06-29 21:01 ` Tom Tromey
2018-06-29 23:04 ` Joel Brobecker
2018-06-30 17:41 ` Pedro Alves
2018-08-23 16:01 ` Simon Marchi
2018-08-23 20:04 ` Tom Tromey [this message]
2018-08-23 20:42 ` Simon Marchi
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=8736v43l6b.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=roirand@adacore.com \
--cc=simon.marchi@polymtl.ca \
/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