From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.help Subject: Re: Using 'git bisect' to pinpoint errors in .emacs. Was: Fatal error 11: Segmentation Fault Date: Wed, 03 Apr 2019 17:47:53 +0200 Message-ID: <86ef6jrsye.fsf@zoho.eu> References: <86imvx5gyz.fsf@zoho.eu> <86ef6l5dwk.fsf@zoho.eu> <86a7h85ru5.fsf@zoho.eu> <865zrw55gm.fsf@zoho.eu> <5e7fb661-c090-4893-bcab-24ee4d96bea3@default> <86ftqzhd04.fsf@zoho.eu> <20190403081845.GA6609@tuxteam.de> <1spnq3gy4i.fsf_-_@uninett.no> <837ecbe0eb.fsf@gnu.org> <867ecbxhsg.fsf@zoho.eu> <834l7fdrkl.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="48610"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Apr 03 18:00:23 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hBiJI-000CTM-Nj for geh-help-gnu-emacs@m.gmane.org; Wed, 03 Apr 2019 18:00:20 +0200 Original-Received: from localhost ([127.0.0.1]:55522 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hBiJH-0004VT-Jv for geh-help-gnu-emacs@m.gmane.org; Wed, 03 Apr 2019 12:00:19 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:54384) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hBiIZ-0003za-05 for help-gnu-emacs@gnu.org; Wed, 03 Apr 2019 11:59:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hBi7O-0004MC-2L for help-gnu-emacs@gnu.org; Wed, 03 Apr 2019 11:48:03 -0400 Original-Received: from [195.159.176.226] (port=53274 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hBi7N-00042f-OX for help-gnu-emacs@gnu.org; Wed, 03 Apr 2019 11:48:02 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1hBi7K-0014qD-6q for help-gnu-emacs@gnu.org; Wed, 03 Apr 2019 17:47:58 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Mail-Copies-To: never Cancel-Lock: sha1:f8u+Fu2Y7STbWCrwjivKs4fsWug= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:119876 Archived-At: Eli Zaretskii wrote: >> Is there a way to disable this or to get >> back to Emacs which is still run? > > When that happens, Emacs _asks_ you whether > to abort and dump core. You don't have to > answer YES. OK, then what happens to me is something else. Emacs gets buried as a bg process. I never cared for that fg and bg stuff anyway, as I don't see the benefit (maybe I'm blind?). Perhaps there is an easy way to get back to Emacs, but because it happens so rarely, so far I've just killed it and started over. I doesn't feel like the right thing to do, but at least I blame my poor uptime on it. $ uptime 17:45:12 up 1 day, 14:33, 14 users, load average: 0.10, 0.09, 0.03 Oh, wait! That's the system uptime, not ERC #emacs ditto... -- underground experts united http://user.it.uu.se/~embe8573