From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Pieter van Oostrum Newsgroups: gmane.emacs.bugs Subject: bug#39962: 27.0.90; Crash in Emacs 27.0.90 Date: Sat, 07 Mar 2020 16:49:46 +0100 Message-ID: References: <24162.58107.725366.668639@cochabamba.vanoostrum.org> <835zfgbo6f.fsf@gnu.org> <83lfoc9upz.fsf@gnu.org> <83ftek9ot8.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="12178"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.90 (darwin) Cc: 39962@debbugs.gnu.org, pieter@vanoostrum.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Mar 07 16:50: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 1jAbiO-00034e-1N for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 07 Mar 2020 16:50:12 +0100 Original-Received: from localhost ([::1]:49954 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jAbiN-0002rm-3U for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 07 Mar 2020 10:50:11 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37614) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jAbiF-0002ra-8z for bug-gnu-emacs@gnu.org; Sat, 07 Mar 2020 10:50:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jAbiE-0007yP-5P for bug-gnu-emacs@gnu.org; Sat, 07 Mar 2020 10:50:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:41444) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jAbiE-0007yF-2N for bug-gnu-emacs@gnu.org; Sat, 07 Mar 2020 10:50:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jAbiE-0008Mg-0h for bug-gnu-emacs@gnu.org; Sat, 07 Mar 2020 10:50:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Pieter van Oostrum Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 07 Mar 2020 15:50:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 39962 X-GNU-PR-Package: emacs Original-Received: via spool by 39962-submit@debbugs.gnu.org id=B39962.158359619732140 (code B ref 39962); Sat, 07 Mar 2020 15:50:01 +0000 Original-Received: (at 39962) by debbugs.gnu.org; 7 Mar 2020 15:49:57 +0000 Original-Received: from localhost ([127.0.0.1]:47417 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jAbi8-0008MJ-MY for submit@debbugs.gnu.org; Sat, 07 Mar 2020 10:49:56 -0500 Original-Received: from [145.132.212.31] (port=52185 helo=cochabamba.vanoostrum.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jAbi6-0008M2-Cs for 39962@debbugs.gnu.org; Sat, 07 Mar 2020 10:49:55 -0500 Original-Received: from cochabamba.vanoostrum.org (localhost [IPv6:::1]) by cochabamba.vanoostrum.org (Postfix) with ESMTP id 71B11AA7FC09; Sat, 7 Mar 2020 16:49:47 +0100 (CET) In-Reply-To: <83ftek9ot8.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 07 Mar 2020 17:17:55 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 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:177015 Archived-At: Eli Zaretskii writes: >> From: Pieter van Oostrum >> Cc: 39962@debbugs.gnu.org, pieter@vanoostrum.org >> Date: Sat, 07 Mar 2020 16:06:09 +0100 >> >> (gdb) f 2 >> #2 0x0000000100233af4 in adjust_markers_for_insert (from=36399, >> from_byte=36399, to=36401, to_byte=36401, before_markers=false) >> at insdel.c:294 >> 294 eassert (m->bytepos >= m->charpos >> (gdb) p m >> $1 = (struct Lisp_Marker *) 0x1609db830 >> (gdb) p m->bytepos >> $2 = 11538 >> (gdb) p m->charpos >> $3 = 0 >> (gdb) p Z_BYTE >> No symbol "Z_BYTE" in current context. >> (gdb) p Z >> No symbol "Z" in current context. >> (gdb) p current_buffer->text->z_byte >> No symbol "current_buffer" in current context. >> (gdb) p current_buffer >> No symbol "current_buffer" in current context. >> (gdb) p current_thread->m_current_buffer >> $4 = (struct buffer *) 0x15b29a4b0 >> (gdb) p current_thread->m_current_buffer->text->z_byte >> $5 = 529784 >> (gdb) p current_thread->m_current_buffer->text->z >> $6 = 529778 >> (gdb) > > Thanks. Could it be that the marker in question is from another > buffer? How does m->buffer compare with > current_thread->m_current_buffer? They are the same. >> > Also note that this is no longer in GC, at least not directly. >> >> That's right. Although the cause of this might also have caused the GC >> problem when the assertion would not have caught it. > > Are you saying that GC is somewhere up the call-stack? If so, can > you show that? No. What I meant is: if this is some kind of corruption of a data structure and if it wouldn't have been caught by the assertion it might later have caused problem in GC. -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]