From: prj@po.cwru.edu (Paul Jarc)
Cc: guile-user@gnu.org
Subject: Re: Customized error reports
Date: Fri, 28 Feb 2003 13:06:02 -0500 [thread overview]
Message-ID: <m3wujkwa8v.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <Pine.GSO.3.96.1030227130754.7799E-100000@anh> (Joris van der Hoeven's message of "Thu, 27 Feb 2003 13:17:57 +0100 (MET)")
Joris van der Hoeven <TeXmacs@math.u-psud.fr> wrote:
> Is it possible to let customized error reports display
> the file name and line number of an object of my choice,
> and not the expression which raised the error.
In a lazy-catch handler, you can use (make-stack #t your-handler) to
create a stack object, and then inspect its frames to see where you
think the error might be. When you find the evaluation frame in
question, you can use frame-source to get the list expression, and
then use source-properties to get the filename, line, and column where
that list came from. See the Debugging node in the manual for more.
paul
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-02-28 18:06 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 [this message]
2003-04-26 14:51 ` PLEASE: debugging embedded guile code Neil Jerram
2003-04-26 16:40 ` 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=m3wujkwa8v.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=guile-user@gnu.org \
/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).