From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: gdb doesn't print Lisp backtrace in some circumstances. Date: Fri, 12 Apr 2024 18:08:05 +0300 Message-ID: <86edbasjoq.fsf@gnu.org> References: <86pluusunr.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3569"; mail-complaints-to="usenet@ciao.gmane.io" Cc: acm@muc.de, emacs-devel@gnu.org To: Gerd =?utf-8?Q?M=C3=B6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Apr 12 17:09:00 2024 Return-path: 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 ) id 1rvIWM-0000Qg-Qg for ged-emacs-devel@m.gmane-mx.org; Fri, 12 Apr 2024 17:08:54 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rvIVf-0003RR-L8; Fri, 12 Apr 2024 11:08:11 -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 ) id 1rvIVe-0003RE-7Q for emacs-devel@gnu.org; Fri, 12 Apr 2024 11:08:10 -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 ) id 1rvIVd-0002Tx-0b; Fri, 12 Apr 2024 11:08:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=aiTd5MDYmHoADCKB4e9JRQVMFEl75GMhV+1jcEgQBPk=; b=fE/RSvKz/exWw7vC4LaP YtaI5hG2+1bVmbwMVo2zjj6NnlM1D2c0dooOwOIwifyqMcSMUrhlymL6bLb2dOCjpfUSZdZqMfR/H Ut8PESFfjPb2VnhDMKK8OEhtzQ/UMy/rqTvHQ9QCk8zNnbovUtTVlCKy42hcPUkdLbqiXeWPTgHYb D+VxD8QyY6HsNjw3qzmob7ZIlFRz4Zp+qpCNE6gnNyHg71PypttJft5QrcyFSFmEy7vrGFCG5M9NU e7l5k4zpOnvGm70vQaUBeKuLFBpWOOYcof4cYZ+QMu2rUhLJ1xSixcg0kRDa0oL8jA25heNwW3EvU XqbXcxSY9Zjk4w==; In-Reply-To: (message from Gerd =?utf-8?Q?M?= =?utf-8?Q?=C3=B6llmann?= on Fri, 12 Apr 2024 16:56:58 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-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:317697 Archived-At: > From: Gerd Möllmann > Cc: Alan Mackenzie , emacs-devel@gnu.org > Date: Fri, 12 Apr 2024 16:56:58 +0200 > > Gerd Möllmann writes: > > > I think it's easier to go through the specbinding stack > > (current_thread->m_specdl). For LLDB, I did that in the xbacktrace > > function in etc/emacs_lldb.py. > > It just remembered that the very first xbacktrace I added did it in a > similar way, so a very old .gdbinit may contain something of a starting > point. Printing Lisp objects would still be a problem, though, even if the backtrace is shown.