unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61960@debbugs.gnu.org, hi-angel@yandex.ru
Subject: bug#61960: 30.0.50; Unexec build reliably crashes during loadup
Date: Tue, 07 Mar 2023 14:59:24 +0000	[thread overview]
Message-ID: <xjf7cvsmwtv.fsf@ma.sdf.org> (raw)
In-Reply-To: <83o7p57mz1.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 06 Mar 2023 20:29:06 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: 61960@debbugs.gnu.org, Konstantin Kharlamov <hi-angel@yandex.ru>
>> Date: Mon, 06 Mar 2023 17:12:55 +0000
>> 
>> > debugging session :) Yeah, if native compilation isn't supposed to work with
>> > unexec(), it might be a good idea to disable that, sure.
>> 
>> Eli related to this, do you think is better to install the attached on
>> 29 or master?
>
> Don't we already have an equivalent test?
>
>   if test "${with_native_compilation}" != "no"; then
>       if test "${HAVE_PDUMPER}" = no; then
> 	 AC_MSG_ERROR(['--with-native-compilation' requires '--with-dumping=pdumper'])
>       fi

So IIUC we can compile emacs with both unexec and pdumper support, they
are not mutually exclusive, and we can specify which one to use for the
first dump with --with-dumping.

So yeah I think we have to prevent native compilation to be compiled
with unexec support, even if it's not the way Emacs is dumped the first
time.

  Andrea





  reply	other threads:[~2023-03-07 14:59 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 [this message]
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=xjf7cvsmwtv.fsf@ma.sdf.org \
    --to=akrl@sdf.org \
    --cc=61960@debbugs.gnu.org \
    --cc=eliz@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).