unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Felipe Lema <felipelema@mortemale.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: capture error stacktrace as sexp?
Date: Wed, 22 Dec 2021 14:37:10 -0300	[thread overview]
Message-ID: <16738737.LcY1orlIAo@felipe-thinkpad-x200> (raw)
In-Reply-To: <jwvzgos4kle.fsf-monnier+emacs@gnu.org>

On Wednesday, 22 December 2021 14.28.53 -03 Stefan Monnier wrote:
> 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
> 
> 
Thanks for the info,  Stefan... I think this list (which includes the symbols and arguments) should be enough information for user.






      reply	other threads:[~2021-12-22 17:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 18:13 capture error stacktrace as sexp? Felipe Lema
2021-12-22 17:28 ` Stefan Monnier
2021-12-22 17:37   ` Felipe Lema [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16738737.LcY1orlIAo@felipe-thinkpad-x200 \
    --to=felipelema@mortemale.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).