From: Gregor Zattler <telegraph@gmx.net>
To: Andrea Corallo <akrl@sdf.org>
Cc: 45603@debbugs.gnu.org
Subject: bug#45603: 28.0.50; feature_native-comp: Fatal error 11: Segmentation fault
Date: Sat, 2 Jan 2021 14:40:21 +0100 [thread overview]
Message-ID: <20210102134021.GA6679@no.workgroup> (raw)
In-Reply-To: <xjflfdbinyj.fsf@sdf.org>
Hi Andrea,
* Andrea Corallo <akrl@sdf.org> [02. Jan. 2021]:
> Gregor Zattler <telegraph@gmx.net> writes:
> > Compiling /home/grfz/src/emacs-feature_native-comp/lisp/emacs-lisp/cl-macs.el...
> > Fatal error 11: Segmentation fault
> > Backtrace:
> > /home/grfz/src/emacs-feature_native-comp/src/emacs[0x58bed0]
[...]
> > Compilation finished.
> >
> > This is with CFLAGS -g -O3 and comp-speed = 3.
> Uhmm... Was the repo in a clean state?
yes, absolutely, I did a rm -rf * ; git checkout -f before building.
> Also have you tried a regular bootstrap at speed 2? Speed 3 bootstrap
> is typically untested.
I did not do it this time. I am in the process of re-doing it with -g
-O2 and comp-speed = 2 and will report back when this finishes.
Ciao, Gregor
--
-... --- .-. . -.. ..--.. ...-.-
next prev parent reply other threads:[~2021-01-02 13:40 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 [this message]
[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
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=20210102134021.GA6679@no.workgroup \
--to=telegraph@gmx.net \
--cc=45603@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).