From: "Marco Maggi" <marco.maggi-ipsu@poste.it>
Subject: saving and restoring the error stack trace
Date: Thu, 24 Aug 2006 21:34:35 +0200 [thread overview]
Message-ID: <J4IP1N$B760770539AC47A2E3D8EFBF9BB44CBC@poste.it> (raw)
Ciao,
I am interfacing the GSL ordinary differential
equations solver with Guile. I have the following
stack of invocations:
my-scheme-implemented-scheme-function
|
->my-C-implemented-scheme-function
|
->gsl_odeiv_evolve_apply
|
->my_C_callback
|
->scm_internal_catch
|
->my_other_C_callback
|
->my-other-scheme-impl-scheme-function
If an error occurs in the invocation of
my-other-scheme-impl-scheme-function I want a
full stack trace of the error be shown to the
user that invoked my-scheme-implemented-scheme-function
at the REPL.
I cannot let the dynwind mechanism pass through
gsl_odeiv_evolve_apply, that is why I am using
scm_internal_catch. But in this way if I rethrow
the exception in my-C-implemented-scheme-function
I loose the stack trace that includes the body
of my-other-scheme-impl-scheme-function.
For the ones that know how Tcl works: what I want
is the same as saving the "errorInfo" global variable
and restoring it later.
Is there a way?
--
Marco Maggi
"They say jump!, you say how high?"
Rage Against the Machine - "Bullet in the Head"
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2006-08-24 19:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 19:34 Marco Maggi [this message]
2006-08-24 21:53 ` saving and restoring the error stack trace Neil Jerram
-- strict thread matches above, loose matches on Subject: below --
2006-08-25 9:39 Marco Maggi
2006-08-27 12:53 ` Neil Jerram
2006-08-28 22:21 ` Neil Jerram
2006-09-07 9:02 ` Volkan YAZICI
2006-09-07 21:36 ` Neil Jerram
2006-09-08 6:09 ` Volkan YAZICI
2006-08-29 3:08 dsmich
2006-09-01 7:34 ` Neil Jerram
2006-08-31 6:04 Marco Maggi
2006-09-01 7:47 ` Neil Jerram
2006-09-01 9:39 ` Ludovic Courtès
2006-09-07 22:11 ` Neil Jerram
2006-09-01 20:10 Marco Maggi
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='J4IP1N$B760770539AC47A2E3D8EFBF9BB44CBC@poste.it' \
--to=marco.maggi-ipsu@poste.it \
/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.
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).