From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: capture error stacktrace as sexp? Date: Wed, 22 Dec 2021 12:28:53 -0500 Message-ID: References: <5546628.DvuYhMxLoT@felipe-thinkpad-x200> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40872"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Felipe Lema Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Dec 22 18:30:34 2021 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 1n05Rh-000AOD-4G for ged-emacs-devel@m.gmane-mx.org; Wed, 22 Dec 2021 18:30:33 +0100 Original-Received: from localhost ([::1]:39200 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n05Rf-0007rJ-RN for ged-emacs-devel@m.gmane-mx.org; Wed, 22 Dec 2021 12:30:31 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:48982) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n05QK-0006Zi-44 for emacs-devel@gnu.org; Wed, 22 Dec 2021 12:29:08 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:54524) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n05QH-0000RH-Bn for emacs-devel@gnu.org; Wed, 22 Dec 2021 12:29:07 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 8796C805EF; Wed, 22 Dec 2021 12:29:03 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id D47CF80552; Wed, 22 Dec 2021 12:29:01 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1640194141; bh=xk3u9Ve3n1zGPW4JzclMfnj1eSXy5sDPOgJPPrJpgrw=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=QIIpocZembuHS+9seK8WnYKUFyuH61J1981T8TYHgWMaDHiiwy+U7kLM0DRm3jQSB iwBaZa20JmxWrIkPqq7iViXvxyqb+54hOFFSNx13NBtNvTihrpiqv+fKRGRHKz99b3 c0UZRh198bQwnCK0SMnfztdoOQxBtZAL6Gj3gdn9RKiulZkoW5kbEz890abpJ435QL ROjoLRgDUWqa+9bfpHvqih9Xm5BXknxDjF/RF+Dz0UyoHmoQqgOTaPRhaefHamCbi9 ZsThb42A5+snJrXr+9wZYFoqb/xBEirAluAja6ChxEWtYCgDOMCBZRYvgx8YXjpwEp UR5PKjeZAi6QA== Original-Received: from pastel (unknown [216.154.30.173]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 7A5781201FF; Wed, 22 Dec 2021 12:29:01 -0500 (EST) In-Reply-To: <5546628.DvuYhMxLoT@felipe-thinkpad-x200> (Felipe Lema's message of "Thu, 16 Dec 2021 15:13:01 -0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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" Xref: news.gmane.io gmane.emacs.devel:282797 Archived-At: Felipe Lema [2021-12-16 15:13:01] wrote: > Hello, there > > Is there a way that, given an `(error ...)` when evaluation some elisp code > one could capture the whole stacktrace as a sexp? > > My intention is to serialize not only the error but the stacktrace of an > error that occurs in a separate Emacs process so I can re-raise the error in > /current/ process. You can find more info and context of my intents here: > https://melpa.org/#/session-async I don't think you can "re-raise" the error in another session in a way that preserves the stack trace, since that would mean preserving the actual whole stack. But you can get the current stacktrace with `backtrace-frames` so you can display it in another session. Stefan