From: Bruce Korb <bkorb@veritas.com>
Cc: Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: PLEASE: debugging embedded guile code
Date: Fri, 16 May 2003 14:56:46 -0700 [thread overview]
Message-ID: <3EC55E9E.12D907E0@veritas.com> (raw)
In-Reply-To: 87fzneoadk.fsf@raven.i.defaultvalue.org
Rob Browning wrote:
> I think perhaps this:
>
> >> SCM str = gh_str02scm( "...whatever..." );
> >> SCM proc = scm_c_lookup( "eval-client-input" );
> >> scm_call_1(proc, str);
>
> Should be
>
> SCM str = gh_str02scm( "...whatever..." );
> SCM proc_var = scm_c_lookup( "eval-client-input" );
> scm_call_1(SCM_VARIABLE_REF(proc), str);
>
> I believe scm_c_lookup returns variables rather than values.
Better! But:
../agen5/autogen -L ../autoopts -Taginfo -bcolumns -DLEVEL=section \
../columns/opts.def
ERROR: Unbound variable: stack-catch
ABEND-ing in LOAD_TPL state
Failing Guile command: = = = = =
(setenv "SHELL" "/bin/sh")
* * * * * * * * * * * * * * * * *
What is the "stack-catch" thing?
Should it be pre-defined by Guile? Is it obsolete?
Thanks!! - Bruce
P.S. Here's the definition for eval-client-input
that was suggested to me:
(define (eval-client-input str)
(stack-catch #t
(lambda ()
(call-with-input-string str
(lambda (p)
(set-port-filename! p (tpl-file))
(set-port-line! p (string->number (tpl-file-line "%2$d")))
(list (primitive-eval (read p))))))
(lambda (key . args)
(apply display-error
(fluid-ref the-last-stack)
(current-error-port)
args)
(set! stack-saved? #f)
#f
) ) )
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-16 21:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.3.96.1030209200016.26546A-100000@anh>
2003-02-25 14:19 ` PLEASE: debugging embedded guile code Joris van der Hoeven
2003-02-25 14:36 ` Dale P. Smith
2003-04-26 14:51 ` 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-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 [this message]
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-30 0:13 ` SRFI 34 Neil Jerram
2003-05-17 0:45 ` Marius Vollmer
2003-05-17 9:39 ` Neil Jerram
2003-05-17 20:36 ` Marius Vollmer
2004-03-07 18:34 ` Neil Jerram
2003-04-26 14:45 ` PLEASE: debugging embedded guile code Neil Jerram
[not found] <Pine.GSO.4.33.0304261706460.1619-100000@sunanh>
2003-04-26 15:34 ` Neil Jerram
2003-04-26 15:40 ` Joris van der Hoeven
2003-04-26 19:30 ` Neil Jerram
2003-04-27 8:40 ` Joris van der Hoeven
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=3EC55E9E.12D907E0@veritas.com \
--to=bkorb@veritas.com \
--cc=neil@ossau.uklinux.net \
/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).