From: Eli Zaretskii <eliz@gnu.org>
To: Konstantin Kharlamov <hi-angel@yandex.ru>
Cc: 61960@debbugs.gnu.org
Subject: bug#61960: 30.0.50; Unexec build reliably crashes during loadup
Date: Sun, 05 Mar 2023 07:46:40 +0200 [thread overview]
Message-ID: <83bkl7agxr.fsf@gnu.org> (raw)
In-Reply-To: <62049aa9ffcf9f39fd423fb87cd8dc8e0b77f9b8.camel@yandex.ru> (message from Konstantin Kharlamov on Sat, 04 Mar 2023 22:50:12 +0300)
> From: Konstantin Kharlamov <hi-angel@yandex.ru>
> Date: Sat, 04 Mar 2023 22:50:12 +0300
>
> So, just to add some points: apparently it isn't so easy to reproduce. I built Emacs with unexec without first looking at the `./configure` line in the report (looking at the report I apparently lack the `with-dumping=unexec`), and removed the workaround to not have BLOCK_SIZE=2¹⁵ if HAVE_UNEXEC. (worth noting probably that I first did the build, then remembered I had to remove the work around installed on master branch, then re-built emacs without the workaround).
>
> Running `emacs` as well as running the `temacs` command ain't shows no crashes.
>
> My configuration was: --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib --localstatedir=/var --mandir=/usr/share/man --with-gameuser=:games --with-modules --without-libotf --without-m17n-flt --without-gconf --enable-link-time-optimization --with-native-compilation=yes --with-xinput2 --with-x-toolkit=gtk3 --without-xaw3d --with-sound=no --with-tree-sitter --without-gpm --without-compress-install '--program-transform-name=s/\\([ec]tags\\)/\\1.emacs/' 'CFLAGS=-flto=2 -march=native -O3 -pipe -fno-stack-protector -fweb -fmerge-all-constants -fno-plt -fcommon' 'LDFLAGS=-flto=2 -O3 -march=native -fweb -fmerge-all-constants -floop-nest-optimize -Wl,--sort-common,-z,relro -fno-plt -fcommon'
>
> I will try to reconfigure build with the flags Eli reports. I seems to have lacked `with-dumping=unexec` option, but I'll try running `configure` only with the flags mentioned, just for the safe case.
My reproduction is with all the *.elc files removed:
$ find ./lisp -name '*.elc' -delete
$ make -j4
The specific versions of the compiler, glibc, and the Linux kernel I
have there could also be relevant, although I'm not sure.
next prev parent reply other threads:[~2023-03-05 5:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 14:55 bug#61960: 30.0.50; Unexec build reliably crashes during loadup Eli Zaretskii
2023-03-04 19:50 ` Konstantin Kharlamov
2023-03-04 19:51 ` Konstantin Kharlamov
2023-03-04 20:05 ` Konstantin Kharlamov
2023-03-04 20:26 ` Konstantin Kharlamov
2023-03-05 5:52 ` Eli Zaretskii
[not found] ` <xjf4jr0xkar.fsf@ma.sdf.org>
2023-03-04 21:56 ` Konstantin Kharlamov
2023-03-04 22:00 ` Konstantin Kharlamov
2023-03-04 22:08 ` Konstantin Kharlamov
2023-03-04 23:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-05 5:59 ` Eli Zaretskii
[not found] ` <xjf7cvtx0q0.fsf@ma.sdf.org>
2023-03-06 18:29 ` Eli Zaretskii
2023-03-07 14:59 ` Andrea Corallo
2023-03-07 15:33 ` Eli Zaretskii
2023-03-11 7:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <xjfpm9es4qe.fsf@ma.sdf.org>
2023-03-12 23:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <xjf3566s29a.fsf@ma.sdf.org>
2023-03-15 13:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-15 14:26 ` Eli Zaretskii
2023-03-16 0:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-16 6:25 ` Eli Zaretskii
[not found] ` <xjfv8j2qe69.fsf@ma.sdf.org>
2023-03-16 0:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-16 6:26 ` Eli Zaretskii
2023-03-05 5:46 ` Eli Zaretskii [this message]
2023-07-02 1:50 ` Konstantin Kharlamov
2023-07-02 2:27 ` Konstantin Kharlamov
2023-07-02 5:52 ` Eli Zaretskii
2023-07-02 11:32 ` Konstantin Kharlamov
2023-07-02 11:54 ` Konstantin Kharlamov
2023-07-02 14:10 ` Konstantin Kharlamov
2023-07-21 16:09 ` Konstantin Kharlamov
2023-07-21 16:30 ` Eli Zaretskii
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=83bkl7agxr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61960@debbugs.gnu.org \
--cc=hi-angel@yandex.ru \
/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).