From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: gdb doesn't print Lisp backtrace in some circumstances.
Date: Fri, 12 Apr 2024 16:24:53 +0300
Message-ID: <86jzl2sogq.fsf@gnu.org>
References: <ZhkNmb8ypVVLs3XV@ACM> <86pluusunr.fsf@gnu.org>
 <ZhkbGdebUY4DOQzA@ACM>
 <86mspyss94.fsf@gnu.org> <Zhk0l7fc1vXYa2eD@ACM>
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="22123"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: emacs-devel@gnu.org
To: Alan Mackenzie <acm@muc.de>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Apr 12 15:27:41 2024
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane-mx.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1rvGwP-0005XM-Fd
	for ged-emacs-devel@m.gmane-mx.org; Fri, 12 Apr 2024 15:27:41 +0200
Original-Received: from localhost ([::1] helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces@gnu.org>)
	id 1rvGu4-0003Cr-Mk; Fri, 12 Apr 2024 09:25:16 -0400
Original-Received: from eggs.gnu.org ([2001:470:142:3::10])
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>) id 1rvGty-00039O-9Z
 for emacs-devel@gnu.org; Fri, 12 Apr 2024 09:25:11 -0400
Original-Received: from fencepost.gnu.org ([2001:470:142:3::e])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1rvGtx-0007ET-DG; Fri, 12 Apr 2024 09:25:09 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
 mime-version; bh=2Kdwme9fGk6gD/C0HeCHCIVknBI76d3n7MiW0Xzfzcw=; b=CepiSxLCQHXv
 bIhyKpkvXF8Qk9akjZISA0MES0XM3mo7JgBILePqUQ7lSlr7SFY7bPlXOibReoDxCEBPVIMa2yNMv
 1m2Ea2r5tdTGD1dzygKu48TofknTdOE+i56s4evRtrrtNWvhJ5W+sfoh//1KgU4ks6KopgNmjxsqm
 I7oZdQcAUl4HHwo8I7s0CSTjt/zeYA56lqGJu58aNXfDfH0bUuRiRlESPBn2/Tyc9d8fGVWIzH/YR
 WtDUSoL1WDGRf1n6Wkv1+1xwibmEsk8MfweRdt0goovAyxQYGXAVW2UIaH83CuuKhR1Nysu+h1UFt
 /w5XXwxv4d2m6RoCw2g1+w==;
In-Reply-To: <Zhk0l7fc1vXYa2eD@ACM> (message from Alan Mackenzie on Fri, 12
 Apr 2024 13:18:15 +0000)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Xref: news.gmane.io gmane.emacs.devel:317694
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/317694>

> Date: Fri, 12 Apr 2024 13:18:15 +0000
> Cc: emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
> 
> > One way of avoiding all this tedious manual work is to try to catch
> > the problem with a breakpoint in a running Emacs, not in a core dump.
> 
> That won't work for this situation.  The seg fault is happening whilst
> loading isearch.el from loadup.el during early building.  I don't have a
> running Emacs to probe it with.

I don't see why can't you have a running Emacs.  You just need to run
temacs under GDB instead of emacs, and you need to run the exact
command that crashes under GDB.  To see what command crashes, run
"make V=1", to force make to display every command it runs in its
entirety.