From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Sudarshan Gaikaiwari Newsgroups: gmane.emacs.bugs Subject: bug#24417: 25.1; Emacs crashes during gc Date: Thu, 29 Sep 2016 11:11:16 -0500 Message-ID: References: <8737l5kgem.fsf@asha.i-did-not-set--mail-host-address--so-tickle-me> <83h99l9i78.fsf@gnu.org> <83twdl7yd1.fsf@gnu.org> <8337kioghb.fsf@gnu.org> Reply-To: sudarshan@acm.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: blaine.gmane.org 1475166134 25536 195.159.176.226 (29 Sep 2016 16:22:14 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 29 Sep 2016 16:22:14 +0000 (UTC) Cc: 24417@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Sep 29 18:22:09 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1bpe5q-0004Ra-Uo for geb-bug-gnu-emacs@m.gmane.org; Thu, 29 Sep 2016 18:21:55 +0200 Original-Received: from localhost ([::1]:39119 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpe5p-0000mL-9d for geb-bug-gnu-emacs@m.gmane.org; Thu, 29 Sep 2016 12:21:53 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54920) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpdwO-0008Q5-7z for bug-gnu-emacs@gnu.org; Thu, 29 Sep 2016 12:12:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bpdwI-00019I-RU for bug-gnu-emacs@gnu.org; Thu, 29 Sep 2016 12:12:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:60994) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpdwI-00019E-Ng for bug-gnu-emacs@gnu.org; Thu, 29 Sep 2016 12:12:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bpdwI-000826-Fm for bug-gnu-emacs@gnu.org; Thu, 29 Sep 2016 12:12:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Sudarshan Gaikaiwari Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 29 Sep 2016 16:12:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 24417 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 24417-submit@debbugs.gnu.org id=B24417.147516549230794 (code B ref 24417); Thu, 29 Sep 2016 16:12:02 +0000 Original-Received: (at 24417) by debbugs.gnu.org; 29 Sep 2016 16:11:32 +0000 Original-Received: from localhost ([127.0.0.1]:38951 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bpdvk-00080R-Bj for submit@debbugs.gnu.org; Thu, 29 Sep 2016 12:11:32 -0400 Original-Received: from mail-qt0-f170.google.com ([209.85.216.170]:35978) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bpdve-0007zp-RV for 24417@debbugs.gnu.org; Thu, 29 Sep 2016 12:11:26 -0400 Original-Received: by mail-qt0-f170.google.com with SMTP id r60so24257866qtd.3 for <24417@debbugs.gnu.org>; Thu, 29 Sep 2016 09:11:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:from:date :message-id:subject:to:cc; bh=XG841Sx00++6LNU7gpoSfTIsJLd/+34ChGBryiBXHFo=; b=vys71MBPwbvnns/U6W3rSSani/QJ/0Nl9386lnt0vyuYjnScCiNt7Oh1sPrv8h/yJQ Emy3JcJYIqYEilP7Mlz2u3XUVNvAv8oA3XBmwMlA3jfUCUTNr6orqMbB32rdm+Pq1yiS 7P5BD1dTkAVjzOSA2ClmIhy8cp2Aawj8xjOsSAg/14a4fYgcsPrTnAmlvF1ruwcoSvwE vumIWh7m/2jXN9Fyq+Tt0YwfJUqfO/8JbVQIrXOeGg5mcC+IPPB1RU0WBDemOCx1KKSg z3ueZ5C1JY1rWZ9pI7/lpE1M8IfvzsXYCThjfr16S5hFhIMcAXaLocGoCSDsJiHpVDzx L8Mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:sender:in-reply-to :references:from:date:message-id:subject:to:cc; bh=XG841Sx00++6LNU7gpoSfTIsJLd/+34ChGBryiBXHFo=; b=URFL2i7UsRAmyex05x3kfsUqD9pU+6sJpDGIOsZN4SlWyuu4uqSljOJ244PTjg87Bk 9N9qPZeJvbZXFnKDvS9JLf+dWzHmrFoL/EMdBT0nJee7CnYKOURgs1KgpDkbB6Bum2U7 iCrrnogwVgM63hscnVFXkwQqhW094Yp2KlArqJdqqoVxWusK+xtq5jqFnqS6rdNXbB6T AZ7hDqDjbBgCiRxmN23nyB/3wCz2xMxdEtmz3UgnxzPSv5MeoE0o14JT/bDiPLkano/N Wbi3BbscVJmHbI9HMS8RvJcpxUy1iHRbTV5bFdmpdmpX3zpdS90OcGTWHb6btw9sWA8U r34A== X-Gm-Message-State: AA6/9RnBOub3WAAaAymtOEbg6glYmQ6BRY2QYc2IdwO2JiuZnWsLAfqJLUy2yJdzKDhLhsT47KwLUAV8asgyEg== X-Received: by 10.200.33.197 with SMTP id 5mr2366417qtz.26.1475165476997; Thu, 29 Sep 2016 09:11:16 -0700 (PDT) Original-Received: by 10.140.46.118 with HTTP; Thu, 29 Sep 2016 09:11:16 -0700 (PDT) In-Reply-To: <8337kioghb.fsf@gnu.org> X-Google-Sender-Auth: 3mquPDbd1zET_Z2x84NitQla1yc 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: 208.118.235.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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:123767 Archived-At: I have reopened the gdb session with coredumpctl gdb /usr/local/bin/emacs-25.1 Please let me know the variables whose values I should report. On Thu, Sep 29, 2016 at 10:47 AM, Eli Zaretskii wrote: >> From: Sudarshan Gaikaiwari >> Date: Wed, 28 Sep 2016 19:50:42 -0500 >> Cc: 24417@debbugs.gnu.org >> >> y emacs process crashed again. I was running a debug build as part of >> bug#24417. The back trace indicates that the sefault is in a different >> module. Please let me know if I should file a new bug instead of >> updating this one. >> I was trying to run rgrep when this crash occured. The emacs build is >> of RC2 and not >> the latest release. > > This crash looks differently, but I'm not yet sure if it's a separate > problem, so let's keep them together for now. > > Is this debugging session still alive? If so, I'd like to ask you to > report values of some relevant variables. > > What seems to have happened here is that Emacs was going to report an > error by starting the Lisp debugger. Then, while redrawing the > display triggered by that, some font-lock construct caused the display > engine to call a Lisp function, which eventually called > re-search-forward, and that segfaulted because it got an invalid > string pointer. > > It would be good to know what was the error Emacs wanted to report, > and what function was invoked from redisplay that caused the crash. -- Sudarshan Gaikaiwari www.sudarshan.org sudarshan@acm.org