From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Joris van der Hoeven <TeXmacs@math.u-psud.fr>
Subject: Re: PLEASE: debugging embedded guile code
Date: 26 Apr 2003 15:51:45 +0100 [thread overview]
Message-ID: <m3znmd8g72.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <20030225093608.6a8935f8.dsmith@altustech.com>
>>>>> "Dale" == Dale P Smith <dsmith@altustech.com> writes:
Dale> On Tue, 25 Feb 2003 15:19:54 +0100 (MET)
Dale> Joris van der Hoeven <TeXmacs@math.u-psud.fr> wrote:
>> So: what should I do in order to enable debugging support
>> for embedded Guile code? How can I retrieve the location of
>> a possible error when calling guile code from the main program?
Dale> The answer is lazy-catch. [...]
Dale> Here is how I did it in mod-guile:
Dale> SCM
Dale> mg_lazy_handler(void *data, SCM tag, SCM throw_args)
Dale> {
Dale> SCM eport = scm_current_error_port(); [...]
I'm curious about this because the question of error handling keeps
popping up and I'm wondering whether our current solution is good
enough. (With a strong suspicion that it isn't.)
One thing I'm not sure I understand is why you want (or perhaps need)
to do this lazy-catch in C rather than in Scheme, since it would be
much easier in Scheme. Can you explain?
Thanks,
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-04-26 14:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 11:12 Source locations Joris van der Hoeven
2003-02-08 17:22 ` Wolfgang Jaehrling
2003-02-09 19:05 ` Joris van der Hoeven
2003-02-25 14:19 ` PLEASE: debugging embedded guile code Joris van der Hoeven
2003-02-25 14:36 ` Dale P. Smith
2003-02-27 12:17 ` Customized error reports Joris van der Hoeven
2003-02-28 18:06 ` Paul Jarc
2003-04-26 14:51 ` Neil Jerram [this message]
2003-04-26 16:40 ` PLEASE: debugging embedded guile code Bruce Korb
2003-04-26 19:12 ` Neil Jerram
2003-04-26 20:13 ` Bruce Korb
2003-04-26 22:25 ` Thien-Thi Nguyen
2003-04-27 20:49 ` Neil Jerram
2003-04-27 21:57 ` Bruce Korb
2003-04-28 15:54 ` Paul Jarc
2003-04-28 16:07 ` Bruce Korb
2003-04-28 19:21 ` Neil Jerram
2003-04-28 20:06 ` Bruce Korb
2003-04-28 20:58 ` Neil Jerram
2003-05-16 17:19 ` Bruce Korb
2003-05-16 19:23 ` Neil Jerram
2003-05-16 20:27 ` Bruce Korb
2003-05-16 21:21 ` Rob Browning
2003-05-16 21:56 ` Bruce Korb
2003-05-17 0:31 ` Bruce Korb
2003-05-17 2:33 ` Bruce Korb
2003-05-19 15:00 ` Paul Jarc
2003-04-28 13:52 ` Mikael Djurfeldt
2003-04-28 19:26 ` Neil Jerram
2003-04-26 14:45 ` Neil Jerram
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=m3znmd8g72.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=TeXmacs@math.u-psud.fr \
/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).