From: Joris van der Hoeven <TeXmacs@math.u-psud.fr>
Subject: Catching errors in C/C++ programs
Date: Wed, 5 Feb 2003 20:10:27 +0100 (MET) [thread overview]
Message-ID: <Pine.GSO.3.96.1030205200425.10195A-100000@anh> (raw)
Hi,
I use Guile as an extension language for GNU TeXmacs.
For debugging purposes, I would like to know how to find
the file and the line where a potential error occured,
when executing a lot of Guile code at startup.
I have been playing around a bit with gh_eval_file_with_catch
and similar routines, but I still don't understand how to
retrieve the file names and line numbers of errors.
Can someone help me?
Best wishes, Joris
-----------------------------------------------------------
Joris van der Hoeven <vdhoeven@texmacs.org>
http://www.texmacs.org: GNU TeXmacs scientific text editor
http://www.math.u-psud.fr/~vdhoeven: personal homepage
-----------------------------------------------------------
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
reply other threads:[~2003-02-05 19:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.GSO.3.96.1030205200425.10195A-100000@anh \
--to=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).