unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: Jonas Jelten <jj@sft.lol>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Emacs segfaults when handling wrong_type_argument backtrace
Date: Thu, 30 Mar 2023 18:51:22 +0000	[thread overview]
Message-ID: <xjflejecbth.fsf@ma.sdf.org> (raw)
In-Reply-To: <6178cb5d-e31a-0851-8dbf-cb7be08e8542@sft.lol> (Jonas Jelten's message of "Thu, 30 Mar 2023 18:41:50 +0200")

Jonas Jelten <jj@sft.lol> writes:

> On 2023-03-30 12:30, Eli Zaretskii wrote:
>>> From: Andrea Corallo <akrl@sdf.org>
>>> Cc: Jonas Jelten <jj@sft.lol>, emacs-devel@gnu.org
>>> Date: Thu, 30 Mar 2023 09:36:25 +0000
>>>
>>> Eli if we want to avoid spurious bug reports due to stale eln-cache we
>>> can also increment ABI_VERSION in comp.c.  Not sure is something we want
>>> to do tho.  Please let me know if you think is appropriate in this case.
>> I don't think we need to increment ABI_VERSION to avoid bug reports,
>> no.  Yes, that places additional burden on my and your shoulders
>> (perhaps mainly on yours), but bumping the ABI_VERSION has its own
>> downsides (e.g., it requires recompilation of all the preloaded
>> files), and I don't think this is justified.  People who track
>> development versions and use that for production sessions will have to
>> be prepared to clean up their eln-cache from time to time, when
>> changes like this one are made.
>> 
>
> After clearing the cache it seems to work, thanks, that was easy.
> I assumed that changes in the abi would result in a version bump :)

It results in Emacs changing the directory name of the eln under
eln-cache, this way Emacs would discard all the other elns and produce
new ones.

We usually do that when we change something low level in an incompatible
way in the eln format.  I agree with Eli we should not use that for
cases when a bug might have produced miscompiled elns.

BR

  Andrea



  reply	other threads:[~2023-03-30 18:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 21:54 Emacs segfaults when handling wrong_type_argument backtrace Jonas Jelten
2023-03-30  5:14 ` Eli Zaretskii
2023-03-30  9:36   ` Andrea Corallo
2023-03-30 10:30     ` Eli Zaretskii
2023-03-30 16:41       ` Jonas Jelten
2023-03-30 18:51         ` Andrea Corallo [this message]
2023-03-31 19:01           ` Jonas Jelten
2023-04-01  5:51             ` tomas
2023-04-01  6:11               ` Eli Zaretskii
2023-04-01  8:06                 ` tomas

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=xjflejecbth.fsf@ma.sdf.org \
    --to=akrl@sdf.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jj@sft.lol \
    /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).