From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#41321: 27.0.91; Emacs aborts due to invalid pseudovector objects Date: Sun, 24 May 2020 19:25:14 +0300 Message-ID: <83y2phwb9x.fsf@gnu.org> References: <83zha8cgpi.fsf@gnu.org> <83r1vibmyj.fsf@gnu.org> <83imgublku.fsf@gnu.org> <831rncjuwf.fsf@gnu.org> <83h7w5xvfa.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="89584"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 41321@debbugs.gnu.org, monnier@iro.umontreal.ca To: Pip Cet Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun May 24 18:26:12 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1jctRy-000N9S-JG for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 24 May 2020 18:26:10 +0200 Original-Received: from localhost ([::1]:56822 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jctRx-0007Kp-K0 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 24 May 2020 12:26:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52278) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jctRq-0007JA-Gv for bug-gnu-emacs@gnu.org; Sun, 24 May 2020 12:26:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:55192) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jctRq-00035Y-8i for bug-gnu-emacs@gnu.org; Sun, 24 May 2020 12:26:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jctRq-000292-2J for bug-gnu-emacs@gnu.org; Sun, 24 May 2020 12:26:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 24 May 2020 16:26:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 41321 X-GNU-PR-Package: emacs Original-Received: via spool by 41321-submit@debbugs.gnu.org id=B41321.15903375138187 (code B ref 41321); Sun, 24 May 2020 16:26:02 +0000 Original-Received: (at 41321) by debbugs.gnu.org; 24 May 2020 16:25:13 +0000 Original-Received: from localhost ([127.0.0.1]:38505 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jctR3-00027z-D9 for submit@debbugs.gnu.org; Sun, 24 May 2020 12:25:13 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:44740) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jctR2-00027m-1C for 41321@debbugs.gnu.org; Sun, 24 May 2020 12:25:12 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:34167) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jctQw-0002qO-Ac; Sun, 24 May 2020 12:25:06 -0400 Original-Received: from [176.228.60.248] (port=3660 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jctQu-0002e0-KH; Sun, 24 May 2020 12:25:05 -0400 In-Reply-To: (message from Pip Cet on Sun, 24 May 2020 15:00:36 +0000) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:180901 Archived-At: > From: Pip Cet > Date: Sun, 24 May 2020 15:00:36 +0000 > Cc: Stefan Monnier , 41321@debbugs.gnu.org > > > FTR, I don't use that flavor of MinGW. > > So your flavor is even more broken than what Debian ships? Why _more_ broken? > That's interesting, which flavor is it? mingw.org's MinGW. > > Isn't that strange? Lisp data is allocated via lmalloc, AFAIK, and > > lmalloc is supposed to guarantee LISP_ALIGNMENT alignment. Or am I > > missing something? > > No, it relies on the compile-time constants and never checks. So that is the bug to fix, no? > > I still very much doubt that this has anything to do with stack > > marking during GC, since I've shown in my backtrace that > > current_buffer->overlays_before points to an overlay with invalid > > markers. > > You haven't. Of course, I have.