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.bugs Subject: bug#52141: 29.0.50; Crash during redisplay Date: Sat, 27 Nov 2021 13:20:51 +0200 Message-ID: <83sfvhzvxo.fsf@gnu.org> References: <87o865c13p.fsf.ref@yahoo.com> <87o865c13p.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1542"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 52141@debbugs.gnu.org To: Po Lu Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Nov 27 12:21:18 2021 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 1mqvle-0000G5-QG for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 27 Nov 2021 12:21:18 +0100 Original-Received: from localhost ([::1]:53066 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mqvld-0007PS-S1 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 27 Nov 2021 06:21:17 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:56828) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mqvlO-0007OR-2A for bug-gnu-emacs@gnu.org; Sat, 27 Nov 2021 06:21:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49736) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mqvlN-00056X-PI for bug-gnu-emacs@gnu.org; Sat, 27 Nov 2021 06:21:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mqvlN-0006QL-JB for bug-gnu-emacs@gnu.org; Sat, 27 Nov 2021 06:21:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 27 Nov 2021 11:21:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 52141 X-GNU-PR-Package: emacs Original-Received: via spool by 52141-submit@debbugs.gnu.org id=B52141.163801205224669 (code B ref 52141); Sat, 27 Nov 2021 11:21:01 +0000 Original-Received: (at 52141) by debbugs.gnu.org; 27 Nov 2021 11:20:52 +0000 Original-Received: from localhost ([127.0.0.1]:33049 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mqvlE-0006Po-5M for submit@debbugs.gnu.org; Sat, 27 Nov 2021 06:20:52 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:55988) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mqvlC-0006Pc-AG for 52141@debbugs.gnu.org; Sat, 27 Nov 2021 06:20:50 -0500 Original-Received: from [2001:470:142:3::e] (port=55258 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mqvl7-0004z5-3i; Sat, 27 Nov 2021 06:20:45 -0500 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=VCEBbBBftvsdGnDsA1rUbpNioA1EXK/IV3q+rbIjF1k=; b=avcTflFUMt3b OZ9UeIJ6+imBAZPj0JzLm3vVdYQd8RdY4tJa0h1G3fYkQH0MSeY0fTOkgmdHJvjHVZ1S/IgJXimPr awjKp4MLDFb/RsIRJtzUc2WqvgnQ6rjq4O1ziZO7unaD2+ZExtfQDIoCVYlMKi2Ey1kpmvuwTokMZ U2pTMrLDywGDFa9B4qL4bKOS0xRYckbBmFRo1OnvasvNBJMN1eUc07ZlOh8bTqhlviPu4/C0AJjcV HqarMKGNfYvr6G5N4TiJNc8FVquESodnjW1L9oMJCeOiUvMImMfRDvLWeGVAOD9YEV+8wv19lYhR5 yA1HUkcjK9ZMKIMs7W38Xg==; Original-Received: from [87.69.77.57] (port=2944 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 1mqvl6-0003Lj-QS; Sat, 27 Nov 2021 06:20:45 -0500 In-Reply-To: <87o865c13p.fsf@yahoo.com> (bug-gnu-emacs@gnu.org) 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:220900 Archived-At: > Date: Sat, 27 Nov 2021 19:03:06 +0800 > From: Po Lu via "Bug reports for GNU Emacs, > the Swiss army knife of text editors" > > > I was typing a random document to test something, and I got the > following crash out of the blue: > > #0 0x00007f201abbc85c in __pthread_kill_implementation () at /lib64/libc.so.6 > #1 0x00007f201ab6f6b6 in raise () at /lib64/libc.so.6 > #2 0x000000000041b6aa in terminate_due_to_signal (sig=sig@entry=11, backtrace_limit=backtrace_limit@entry=40) at emacs.c:443 > #3 0x000000000041bb29 in handle_fatal_signal (sig=sig@entry=11) at sysdep.c:1780 > #4 0x000000000051b9d8 in deliver_thread_signal (sig=sig@entry=11, handler=0x41bb1e ) at sysdep.c:1772 > #5 0x000000000051ba49 in deliver_fatal_thread_signal (sig=11) at sysdep.c:1792 > #6 handle_sigsegv (sig=11, siginfo=, arg=) at sysdep.c:1885 > #7 0x00007f201ab6f760 in () at /lib64/libc.so.6 > #8 0x000000000055c6b1 in make_lisp_ptr (type=, ptr=) > at /home/oldosfan/emacs-dev/emacs-gc/src/lisp.h:1269 > #9 set_next_vectorPython Exception : Cannot access memory at address 0xfe94cc8 > (p=#10 setup_on_free_list (nbytes=, v=0x2ce6c10) at alloc.c:2977 > #11 sweep_vectors () at alloc.c:3242 > #12 0x0000000000561328 in gc_sweep () at alloc.c:7255 > #13 garbage_collect () at alloc.c:6190 > #14 0x0000000000561811 in maybe_garbage_collect () at alloc.c:6053 > #15 0x00000000005804ad in maybe_gc () at /home/oldosfan/emacs-dev/emacs-gc/src/lisp.h:5161 > #16 eval_sub (form=0x1e753d3) at eval.c:2449 > #17 0x0000000000582149 in Feval (form=0x1e753d3, lexical=) at eval.c:2372 ^^^^ What is this form we are evaluating here? Can you show its contents? (Not that I think it is related to the crash.) Basically, GC was triggered by that evaluation, and it found some bad memory in some vector that it wanted to put on the free list. The challenge is to determine which Lisp vector caused that bad memory. Try looking at the data in frames 10 and 9 to figure out what was that bad vector.