From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: hi-angel@yandex.ru, 61960@debbugs.gnu.org, akrl@sdf.org
Subject: bug#61960: 30.0.50; Unexec build reliably crashes during loadup
Date: Thu, 16 Mar 2023 08:26:39 +0200 [thread overview]
Message-ID: <83h6ulqkio.fsf@gnu.org> (raw)
In-Reply-To: <87a60d5ycy.fsf@yahoo.com> (message from Po Lu on Thu, 16 Mar 2023 08:33:17 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 61960@debbugs.gnu.org, hi-angel@yandex.ru
> Date: Thu, 16 Mar 2023 08:33:17 +0800
>
> > But you still have to answer my question: where do you read that?
>
> By working with both kinds of dumping while working on the garbage
> collector last year, and then the MS-DOS port earlier. I didn't
> hesitate to assume:
>
> #ifdef HAVE_UNEXEC
>
> #else
>
> #endif /* HAVE_PDUMPER */
>
> My mistake, sorry.
Yes, that is a mistake. These two are not mutually exclusive.
next prev parent reply other threads:[~2023-03-16 6:26 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 [this message]
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=83h6ulqkio.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61960@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=hi-angel@yandex.ru \
--cc=luangruo@yahoo.com \
/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).