This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug jit/64721] SIGABRT becomes a SIGSEGV after invoking gcc_jit_context_compile[_to_file] within a process
- From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 21 Jan 2015 22:18:31 +0000
- Subject: [Bug jit/64721] SIGABRT becomes a SIGSEGV after invoking gcc_jit_context_compile[_to_file] within a process
- Auto-submitted: auto-generated
- References: <bug-64721-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64721
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|SIGABRT becomes a SIGSEGV |SIGABRT becomes a SIGSEGV
|in jit testsuite |after invoking
| |gcc_jit_context_compile[_to
| |_file] within a process
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(retitling; it appears that any use of gcc_jit_context_compile[_to_file] that
makes it as far as toplev::main will install the signal-handlers into the
process, leading to SIGSEGV inside libgccjit due e.g. to assert failures in
other DSOs within the process)