public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1
Date: Thu, 15 Apr 2021 17:44:29 +0000 [thread overview]
Message-ID: <bug-100096-4-2ezNaWWKP4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100096-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096
--- Comment #16 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to Sascha Wilde from comment #10)
> (In reply to David Malcolm from comment #8)
> > It would be good to know exactly where that error message is being emitted.
> >
> > If you add:
> > gcc_jit_context_set_logfile (ctxt, stderr, 0, 0);
> > to the test code (e.g. immediately after the call to
> > gcc_jit_context_acquire), libgccjit ought to spew out a copious amount of
> > logging (see
> > https://gcc.gnu.org/onlinedocs/jit/internals/index.html#example-of-log-file)
> >
> > Can you attach the log you get please?
>
> With security.pax.mprotect.global=1 it produces no extra output.
> I'll attach the output produced when security.pax.mprotect.global is
> disabled.
Thanks! I was wondering if the error message was:
(a) due to a problem dynamically linking libgccjit into the process, or
(b) a later problem with linking the code that libgccjit generates into the
process.
Given that there's no extra log output at all with the protection flag, it
sounds like it's (a) - though you may run into a similar problem with (b)
if/when (a) gets solved.
next prev parent reply other threads:[~2021-04-15 17:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 11:14 [Bug jit/100096] New: " swilde@sha-bang.de
2021-04-15 12:18 ` [Bug jit/100096] " jakub at gcc dot gnu.org
2021-04-15 13:21 ` swilde@sha-bang.de
2021-04-15 13:23 ` jakub at gcc dot gnu.org
2021-04-15 13:30 ` swilde@sha-bang.de
2021-04-15 13:32 ` swilde@sha-bang.de
2021-04-15 13:36 ` swilde@sha-bang.de
2021-04-15 13:38 ` schwab@linux-m68k.org
2021-04-15 13:47 ` dmalcolm at gcc dot gnu.org
2021-04-15 14:03 ` jakub at gcc dot gnu.org
2021-04-15 14:41 ` swilde@sha-bang.de
2021-04-15 14:42 ` swilde@sha-bang.de
2021-04-15 14:58 ` swilde@sha-bang.de
2021-04-15 15:00 ` jakub at gcc dot gnu.org
2021-04-15 15:08 ` jakub at gcc dot gnu.org
2021-04-15 16:13 ` swilde@sha-bang.de
2021-04-15 17:44 ` dmalcolm at gcc dot gnu.org [this message]
2021-04-15 20:07 ` swilde@sha-bang.de
2021-04-16 9:37 ` swilde@sha-bang.de
2021-04-16 9:38 ` swilde@sha-bang.de
2021-04-16 11:28 ` jakub at gcc dot gnu.org
2021-04-16 12:18 ` wilde@sha-bang.de
2021-04-16 12:25 ` jakub at gcc dot gnu.org
2021-04-16 14:32 ` wilde@sha-bang.de
2021-04-16 16:35 ` cvs-commit at gcc dot gnu.org
2021-04-20 9:46 ` cvs-commit at gcc dot gnu.org
2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:53 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:12 ` jakub at gcc dot gnu.org
2021-09-11 14:29 ` pinskia at gcc dot gnu.org
2022-06-27 8:28 ` swilde@sha-bang.de
2023-07-24 8:54 ` swilde@sha-bang.de
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=bug-100096-4-2ezNaWWKP4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).