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: Thoughts on getting correct line numbers in the byte compiler's warning messages Date: Mon, 12 Nov 2018 05:30:55 +0200 Message-ID: <83d0rb9dlc.fsf@gnu.org> References: <20181107170036.GA4934@ACM> <20181107184708.GB4934@ACM> <20181108140843.GB5041@ACM> <20181108221311.GD5041@ACM> <20181111125945.GA6487@ACM> <83k1lja9w6.fsf@gnu.org> <20181111201214.GA8219@ACM> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1541993388 26862 195.159.176.226 (12 Nov 2018 03:29:48 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 12 Nov 2018 03:29:48 +0000 (UTC) Cc: michael_heerdegen@web.de, acm@muc.de, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 12 04:29:44 2018 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 1gM2v1-0006p4-PO for ged-emacs-devel@m.gmane.org; Mon, 12 Nov 2018 04:29:43 +0100 Original-Received: from localhost ([::1]:44604 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gM2x6-0002fm-MM for ged-emacs-devel@m.gmane.org; Sun, 11 Nov 2018 22:31:52 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41645) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gM2wR-0002fV-1n for emacs-devel@gnu.org; Sun, 11 Nov 2018 22:31:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gM2wL-00075L-DB for emacs-devel@gnu.org; Sun, 11 Nov 2018 22:31:10 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:32793) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gM2wK-00073z-Qf; Sun, 11 Nov 2018 22:31:05 -0500 Original-Received: from [176.228.60.248] (port=1503 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gM2wK-0006qW-AM; Sun, 11 Nov 2018 22:31:04 -0500 In-reply-to: (message from Stefan Monnier on Sun, 11 Nov 2018 15:47:19 -0500) 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:231084 Archived-At: > From: Stefan Monnier > Cc: Eli Zaretskii , michael_heerdegen@web.de, > emacs-devel@gnu.org > Date: Sun, 11 Nov 2018 15:47:19 -0500 > > > Another, slightly more honest, answer is that when it wasn't there, my > > Emacs build crashed with a segfault whilst loading .el files. I didn't > > get a core dump for this segfault. Could you please tell me (or point > > me in the right direction of documentation) how I configure my GNU/Linux > > to generate core dumps. I think my kernel's set up correctly, but I > > don't see the dumps. > > I can't rmember how to do that "ulimit -H -c unlimited", I think. > but I recommend you just run emacs (or temacs as the case may be) > within GDB directly rather than go through a core dump. Right.