From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: akrl--- via "Bug reports for GNU Emacs,
the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
Cc: 45603-done@debbugs.gnu.org
Subject: bug#45603: 28.0.50; feature_native-comp: Fatal error 11: Segmentation fault
Date: Thu, 25 Feb 2021 22:42:24 +0000 [thread overview]
Message-ID: <xjfeeh3hir3.fsf@sdf.org> (raw)
In-Reply-To: <xjfzh0svjt7.fsf@sdf.org> (akrl's message of "Thu, 28 Jan 2021 21:21:56 +0000")
akrl--- via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of
> text editors" <bug-gnu-emacs@gnu.org> writes:
>
>> Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of
>> text editors" <bug-gnu-emacs@gnu.org> writes:
>>
>>> Gregor Zattler <telegraph@gmx.net> writes:
>>>
>>>> Both files are attachet.
>>>>
>>>> Thanks for looking into this, Gregor
>>>
>>> Which version of libgccjit are you on?
>>
>> Hi Gregor,
>>
>> in case you have been on a recent (~2 month max) GCC trunk this might be
>> due to <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98615>.
>>
>> Andrea
>>
>>> The odd thing is that it's crashing in libgccjit, but when you built
>>> Emacs it worked for all the bootstrap and initial compilation. I'm
>>> thinking to a reason to justify such difference...
>>>
>>> Is it possible that running Emacs you have some of the libgccjit
>>> sensitive env variable with a different setting?
>>>
>>> These are tipically LD_LIBRARY_PATH LIBRARY_PATH and PATH.
>
> Is this issue persisting?
>
> Andrea
As no update on this was given I'm closing this. Happy to reopen if the
issue is reported to persist.
Thanks
Andrea
prev parent reply other threads:[~2021-02-25 22:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 23:35 bug#45603: 28.0.50; feature_native-comp: Fatal error 11: Segmentation fault Gregor Zattler
2021-01-02 11:21 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-02 13:40 ` Gregor Zattler
[not found] ` <20210102210614.GA7786@no.workgroup>
2021-01-03 20:08 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-03 20:44 ` Gregor Zattler
2021-01-03 21:39 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-11 14:40 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-28 21:21 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-25 22:42 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xjfeeh3hir3.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=45603-done@debbugs.gnu.org \
--cc=akrl@sdf.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).