From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs segfaults when handling wrong_type_argument backtrace Date: Thu, 30 Mar 2023 13:30:23 +0300 Message-ID: <838rfe5y68.fsf@gnu.org> References: <2c65531c-2d9c-3c1d-bc2a-5666a7de0a38@sft.lol> <83zg7u6cs3.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22064"; mail-complaints-to="usenet@ciao.gmane.io" Cc: jj@sft.lol, emacs-devel@gnu.org To: Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Mar 30 12:30:27 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1phpY1-0005UM-TI for ged-emacs-devel@m.gmane-mx.org; Thu, 30 Mar 2023 12:30:26 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1phpXs-0003Ok-9O; Thu, 30 Mar 2023 06:30:16 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1phpXr-0003Oa-4z for emacs-devel@gnu.org; Thu, 30 Mar 2023 06:30:15 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1phpXq-0003WG-FC; Thu, 30 Mar 2023 06:30:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=YRpZMWNucaWJHGxO+QaXsHhQLxdUX0ZSa7uVI5HDymE=; b=Tmy1HbmzY6bW TW1kc9fYMnDOQVQHpxGKLVqPkkmXw0o0xKiymRAsKA48gFZM/Q2J0Tac+TN+ov8pyRs12xNBfJLjW 6WCiXD8y4Z724mevFZKNtHqFi6GxThBgWVx644lVFMwgoxNDnoHxhTNwpUmLS0fuDQcTRyY9DGIQ6 3CPCHxh1Wt2oaB0zxq0pClk4X+Rxf0FTlCAmV/nGfF1wa4p+5cSadPU1+ETkE6tMVsy3qT7zcUN2a Yd725XafQKUu0jluBjXPMkHyEUp6k0ZJza1VqkTVxY/ogr/99uKzY2mITyE/AyZ8TZYsHBQp8GjkG OspJuXqEyq6xPFtaDYyp4w==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1phpXp-0006mQ-As; Thu, 30 Mar 2023 06:30:13 -0400 In-Reply-To: (message from Andrea Corallo on Thu, 30 Mar 2023 09:36:25 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:304855 Archived-At: > From: Andrea Corallo > Cc: Jonas Jelten , 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.