From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Occasional Crash When Running `rgrep` Date: Sun, 08 Jan 2017 22:33:16 +0200 Message-ID: <83r34di96b.fsf@gnu.org> References: <83inpuegd9.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1483907633 21822 195.159.176.226 (8 Jan 2017 20:33:53 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 8 Jan 2017 20:33:53 +0000 (UTC) Cc: emacs-devel@gnu.org To: aditya siram Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 08 21:33:50 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cQK9u-0004QF-Ud for ged-emacs-devel@m.gmane.org; Sun, 08 Jan 2017 21:33:43 +0100 Original-Received: from localhost ([::1]:34968 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cQK9z-0005pX-BI for ged-emacs-devel@m.gmane.org; Sun, 08 Jan 2017 15:33:47 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35646) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cQK9e-0005kd-3M for emacs-devel@gnu.org; Sun, 08 Jan 2017 15:33:27 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cQK9b-0006aj-1Y for emacs-devel@gnu.org; Sun, 08 Jan 2017 15:33:26 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:60938) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cQK9a-0006aa-UT; Sun, 08 Jan 2017 15:33:22 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1226 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cQK9Z-00008A-T4; Sun, 08 Jan 2017 15:33:22 -0500 In-reply-to: (message from aditya siram on Sun, 8 Jan 2017 13:02:21 -0600) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:211167 Archived-At: > From: aditya siram > Date: Sun, 8 Jan 2017 13:02:21 -0600 > Cc: "emacs-devel@gnu.org Development" > > It took a couple of day for it to happen again, but here's the human readable backtrace: > Jan 08 13:01:55 deech-thinkpad systemd-coredump[25660]: Process 27577 (emacs) of user 1000 dumped > core. > > Stack trace of thread 27577: > #0 0x00007efc14652f5f raise (libpthread.so.0) > #1 0x00000000004e33b1 terminate_due_to_signal (emacs-25.1) > #2 0x00000000004fa83e handle_fatal_signal (emacs-25.1) > #3 0x00000000004faa43 deliver_thread_signal (emacs-25.1) > #4 0x00000000004faaaf deliver_fatal_thread_signal (emacs-25.1) > #5 0x00007efc14653080 __restore_rt (libpthread.so.0) > #6 0x00000000004a9fa0 turn_on_face (emacs-25.1) > #7 0x00000000004ae0f2 tty_write_glyphs (emacs-25.1) > #8 0x000000000041904a update_frame_line (emacs-25.1) > #9 0x000000000041c866 update_frame_1 (emacs-25.1) > #10 0x000000000041e08e update_frame (emacs-25.1) > #11 0x0000000000450cd4 redisplay_internal (emacs-25.1) > #12 0x00000000004ed1db read_char (emacs-25.1) > #13 0x00000000004efba0 read_key_sequence (emacs-25.1) > #14 0x00000000004f16c6 command_loop_1 (emacs-25.1) > #15 0x0000000000552c32 internal_condition_case (emacs-25.1) > #16 0x00000000004e37ec command_loop_2 (emacs-25.1) > #17 0x0000000000552bd3 internal_catch (emacs-25.1) > #18 0x00000000004e3750 command_loop (emacs-25.1) > #19 0x00000000004e7d77 recursive_edit_1 (emacs-25.1) > #20 0x000000000050ef5f read_minibuf (emacs-25.1) > #21 0x000000000050f6df Fread_from_minibuffer (emacs-25.1) Thanks. This doesn't look like Emacs was running rgrep, did it? I suggest to try the latest pretest of Emacs 25.2, it could be that this problem is already fixed.