From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: gerd.moellmann@gmail.com, 66743@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#66743: 30.0.50; Crash when dumping reftex
Date: Fri, 27 Oct 2023 14:01:32 +0300 [thread overview]
Message-ID: <83h6mce3cj.fsf@gnu.org> (raw)
In-Reply-To: <87o7gkcp1y.fsf@localhost> (message from Ihor Radchenko on Fri, 27 Oct 2023 10:55:37 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: gerd.moellmann@gmail.com, stefankangas@gmail.com, 66743@debbugs.gnu.org
> Date: Fri, 27 Oct 2023 10:55:37 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> If `error' does all the necessary cleanup, `emacs_abort' is indeed not
> >> necessary. But that's not very obvious from the source code.
> >
> > What cleanup is needed in this case?
>
> I have no idea.
> To be clear: I am not sure what is the difference between `emacs_abort'
> and `error'.
AFAIU, in batch mode there's no difference, since calling 'error'
shows a backtrace and exits.
> If you say that using `error' instead of `emacs_abort' is safe, I will
> just follow. I expect that you know these details well.
I think it's safe, since we already do that in other places in
pdumper.c.
next prev parent reply other threads:[~2023-10-27 11:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 9:46 bug#66743: 30.0.50; Crash when dumping reftex Ihor Radchenko
2023-10-25 12:46 ` Eli Zaretskii
2023-10-25 12:58 ` Ihor Radchenko
2023-10-25 14:44 ` Stefan Kangas
2023-10-26 9:31 ` Ihor Radchenko
2023-10-26 10:01 ` Gerd Möllmann
2023-10-26 11:55 ` Ihor Radchenko
2023-10-26 12:08 ` Eli Zaretskii
2023-10-26 12:14 ` Ihor Radchenko
2023-10-26 13:04 ` Eli Zaretskii
2023-10-26 13:13 ` Ihor Radchenko
2023-10-26 13:18 ` Eli Zaretskii
2023-10-26 13:27 ` Ihor Radchenko
2023-10-26 13:28 ` Eli Zaretskii
2023-10-26 13:48 ` Ihor Radchenko
2023-10-26 15:49 ` Eli Zaretskii
2023-10-27 9:08 ` Ihor Radchenko
2023-10-27 10:38 ` Eli Zaretskii
2023-10-27 10:55 ` Ihor Radchenko
2023-10-27 11:01 ` Eli Zaretskii [this message]
2023-10-27 11:09 ` Ihor Radchenko
2023-10-27 12:36 ` Eli Zaretskii
2023-10-27 12:45 ` Ihor Radchenko
2023-10-27 12:53 ` Eli Zaretskii
2023-10-25 16:15 ` Gerd Möllmann
2023-10-25 16:21 ` Eli Zaretskii
2023-10-25 16:37 ` Gerd Möllmann
2023-10-26 7:03 ` Gerd Möllmann
2023-10-26 7:35 ` Eli Zaretskii
2023-10-26 8:04 ` Gerd Möllmann
2023-10-26 9:38 ` Ihor Radchenko
2023-10-26 9:44 ` 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=83h6mce3cj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66743@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=stefankangas@gmail.com \
--cc=yantar92@posteo.net \
/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).