From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: Andrea Corallo <akrl@sdf.org>
Cc: 61960@debbugs.gnu.org
Subject: bug#61960: 30.0.50; Unexec build reliably crashes during loadup
Date: Sun, 05 Mar 2023 01:00:42 +0300 [thread overview]
Message-ID: <d630a081b8798f950b119bae531628d227d65a06.camel@yandex.ru> (raw)
In-Reply-To: <7a6e37ed07a49a85a51c8a3a40cadc2b752a38ef.camel@yandex.ru>
On Sun, 2023-03-05 at 00:56 +0300, Konstantin Kharlamov wrote:
> On Sat, 2023-03-04 at 21:45 +0000, Andrea Corallo wrote:
> > Konstantin Kharlamov <hi-angel@yandex.ru> writes:
> >
> > > Oh, I am sorry, I posted the configuration line from the wrong emacs
> > > build.
> > > It's
> > > supposed to be:
> > >
> > > --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 --with-native-compilation=yes --with-
> > > xinput2 --
> > > with-x-toolkit=gtk3 --without-xaw3d --with-sound=no --with-tree-sitter --
> > > with-
> > > unexec --without-gpm --without-compress-install 'CFLAGS=-O0 -g3'
> >
> > Hi Konstantin,
> >
> > maybe the crash you see is not related but native-compilation is not
> > supposed to work with unexec builds.
> >
> > I think we should really add a configure time error for this. Eli could
> > this change go to emacs-29?
>
> emacs-29 haven't got the BLOCK_ALIGN change, so is unaffected.
Ah, sorry, I failed to parse your text correctly, because I'm in context of the
debugging session :) Yeah, if native compilation isn't supposed to work with
unexec(), it might be a good idea to disable that, sure.
> I should note though that I'm not the reporter :)
>
> ---------------
>
> Regarding my current findings: apparently the `unexec` has always been broken.
> I built it with sanitizer and found out that the variable `bss_size_growth`
> when doing the dump has too big size. The only difference between "before" and
> "after" the BLOCK_ALIGN change is that the difference "after" became quite
> large. It was just 440 bytes before, and became 31494584 bytes after.
>
> However, when built with sanitizer, sanitizer catches the problem in both
> cases, so there's that.
next prev parent reply other threads:[~2023-03-04 22:00 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 [this message]
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
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=d630a081b8798f950b119bae531628d227d65a06.camel@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=61960@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).