From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Barry OReilly Newsgroups: gmane.emacs.bugs Subject: bug#15794: Core dump after SIGTERM during GC marking Date: Tue, 5 Nov 2013 11:52:09 -0500 Message-ID: References: <87k3gq2dpr.fsf@igel.home> <83d2mh9ydm.fsf@gnu.org> <877gcp2wiz.fsf@igel.home> <83a9hl9sau.fsf@gnu.org> <8738nd2kig.fsf@igel.home> <83zjpk96qr.fsf@gnu.org> <83y554889t.fsf@gnu.org> <83bo1y976a.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0149d0ae77a85f04ea70da12 X-Trace: ger.gmane.org 1383670398 21514 80.91.229.3 (5 Nov 2013 16:53:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 5 Nov 2013 16:53:18 +0000 (UTC) Cc: Andreas Schwab , 15794 <15794@debbugs.gnu.org> To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Nov 05 17:53:21 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VdjsW-00042G-Qs for geb-bug-gnu-emacs@m.gmane.org; Tue, 05 Nov 2013 17:53:21 +0100 Original-Received: from localhost ([::1]:57286 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VdjsW-00028Y-Fv for geb-bug-gnu-emacs@m.gmane.org; Tue, 05 Nov 2013 11:53:20 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50071) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VdjsM-00026y-NP for bug-gnu-emacs@gnu.org; Tue, 05 Nov 2013 11:53:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VdjsF-00035R-0j for bug-gnu-emacs@gnu.org; Tue, 05 Nov 2013 11:53:10 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:50263) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VdjsE-00035N-U8 for bug-gnu-emacs@gnu.org; Tue, 05 Nov 2013 11:53:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1VdjsE-00065p-AC for bug-gnu-emacs@gnu.org; Tue, 05 Nov 2013 11:53:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Barry OReilly Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 05 Nov 2013 16:53:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 15794 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 15794-submit@debbugs.gnu.org id=B15794.138367033823312 (code B ref 15794); Tue, 05 Nov 2013 16:53:02 +0000 Original-Received: (at 15794) by debbugs.gnu.org; 5 Nov 2013 16:52:18 +0000 Original-Received: from localhost ([127.0.0.1]:36049 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VdjrV-00063u-AC for submit@debbugs.gnu.org; Tue, 05 Nov 2013 11:52:17 -0500 Original-Received: from mail-oa0-f46.google.com ([209.85.219.46]:48041) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VdjrT-00063g-7E for 15794@debbugs.gnu.org; Tue, 05 Nov 2013 11:52:15 -0500 Original-Received: by mail-oa0-f46.google.com with SMTP id g12so9000523oah.33 for <15794@debbugs.gnu.org>; Tue, 05 Nov 2013 08:52:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0s70XBiSjCkCCJ9byFAeU7vpbHOUG6OH5ICWtA8X0AU=; b=xoE99YHyyoZ6U4lVPaHUFhDcbYZ6yGcawPndiIK0IciFhl17aBl9hz5fXAcSftu/Ap t1e4DmyzrjnxwxqPQwEcK8MWPD5+MkeJPIq8rxYRmaoRgcZfqThVBnsZnmHSbfrLv+C+ 4w27079ByR+OfC3S/YfWIVOMY5b/j9MQBdpfvBDfzBjGIHFAlaGcQ9E/baDoD/+zwNth czyCt/VZbeYF4omfdiK6OYCTb3mENvSDGrx0jQ1YWR525bz49Vyls9AyrPnebhxw1vzX aa6JK+4E2sLO6L+sPQYvxrIT7Hk7/8APpPT3mXXU9Uug5AcRvzBjFspx3MEXs5GDO7dw 2oRw== X-Received: by 10.60.60.105 with SMTP id g9mr19573904oer.8.1383670329352; Tue, 05 Nov 2013 08:52:09 -0800 (PST) Original-Received: by 10.76.156.103 with HTTP; Tue, 5 Nov 2013 08:52:09 -0800 (PST) In-Reply-To: <83bo1y976a.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.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-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:80031 Archived-At: --089e0149d0ae77a85f04ea70da12 Content-Type: text/plain; charset=ISO-8859-1 Since I can't reproduce the original crash, I am trying other means of gathering evidence. A SIGTERM could be handled at any time right? Including as in this artificial reproduction. > But the Lisp backtrace doesn't tell which function of the > kill-emacs-hook was running, Yes it does. The hook is ede-save-cache. It is one of the two hooks my configuration sets up, as I indicated earlier. > and GC didn't really start doing its job, so it's not exactly the > same crash. It is after gc_in_progress = 1. Are you trying to argue Emacs cannot possibly enter the SIGTERM handler between that and when GC "really starts doing its job" (whenever that is)? > And look at the variable 'args', which should be a list. Since this > session crashed in GC, it is not safe to print Lisp objects with > "pp" and its likes. Instead, you will have to walk the list using > "xcar" and "xcdr", display the type of each object in the list using > "xtype", and then display the object itself with the appropriate x* > command, normally "xsymbol", since the list is constructed from > function symbols. Can this be done for core dump files? --089e0149d0ae77a85f04ea70da12 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Since I can't reproduce the original crash, I am tryin= g other means of
gathering evidence. A SIGTERM could be handled at any t= ime right?
Including as in this artificial reproduction.

> But= the Lisp backtrace doesn't tell which function of the
> kill-emacs-hook was running,

Yes it does. The hook is ede-save-= cache. It is one of the two hooks my
configuration sets up, as I indicat= ed earlier.

> and GC didn't really start doing its job, so it= 's not exactly the
> same crash.

It is after gc_in_progress =3D 1. Are you trying to= argue Emacs cannot
possibly enter the SIGTERM handler between that and = when GC "really
starts doing its job" (whenever that is)?

> And look at the variable 'args', which should be a list. S= ince this
> session crashed in GC, it is not safe to print Lisp objec= ts with
> "pp" and its likes. Instead, you will have to wal= k the list using
> "xcar" and "xcdr", display the type of each object= in the list using
> "xtype", and then display the object i= tself with the appropriate x*
> command, normally "xsymbol"= , since the list is constructed from
> function symbols.

Can this be done for core dump files?

=
--089e0149d0ae77a85f04ea70da12--