From: Eli Zaretskii <eliz@gnu.org>
To: Felix Willgerodt <felix.willgerodt@intel.com>
Cc: gdb@sourceware.org
Subject: Re: Macos notarization and "Unkown signal" on macos
Date: Wed, 04 Sep 2019 15:01:00 -0000 [thread overview]
Message-ID: <83k1ao6r71.fsf@gnu.org> (raw)
In-Reply-To: <49b5919f-6871-d147-4aa9-5f93bedbe571@intel.com> (message from Felix Willgerodt on Wed, 4 Sep 2019 16:32:12 +0200)
> From: Felix Willgerodt <felix.willgerodt@intel.com>
> Date: Wed, 4 Sep 2019 16:32:12 +0200
>
> * darwin_attach_pid(): Added a loop that tries task_for_pid() 10 times,
> sleeping 10000 usec inbetween. This change was inspired by LLDB and
> seems to be necessary for the hardened runtime.
> * darwin_ptrace_me(): Changed the process group setting to occour after
> the ptrace calls (inspired by LLDB)
> * darwin_ptrace_him(): Set the child process group to match its pid
> (inspired by LLDB)
Bother: could "inspired by LLDB" mean that the code was copied from
there? This could mean legal problems if we accept such code.
IOW, how much of the code is actually your own original code?
next prev parent reply other threads:[~2019-09-04 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 14:34 Felix Willgerodt
2019-09-04 15:01 ` Eli Zaretskii [this message]
2019-09-16 8:47 ` Willgerodt, Felix
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=83k1ao6r71.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=felix.willgerodt@intel.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).