From: Han-Wen Nienhuys <hanwen@xs4all.nl>
Subject: Backtraces in modules?
Date: Tue, 03 May 2005 12:56:28 +0200 [thread overview]
Message-ID: <427758DC.1020107@xs4all.nl> (raw)
Hi there,
I have trouble getting backtraces in code evalled within loaded
modules. I do
String mod_nm = "scm framework-" + output_backend_global;
SCM mod = scm_c_resolve_module (mod_nm.to_str0 ());
if (make_print)
{
SCM func = scm_c_module_lookup (mod, "output-framework");
func = scm_variable_ref (func);
scm_apply_0 (func, .. )
iow. I load the scm/framework-foo.scm module, which contains
(define-public (output-framework basename book scopes fields)
(debug-enable 'backtrace)
(foobar)
then I get
Calculating line breaks... [2]ERROR: Unbound variable: foobar
muurbloem:~/src/lilypond$
how do I get a stack trace? I've traced the problem to scm_make_stack(),
which cannot construct a frame, since scm_i_last_debug_frame() returns 0x0.
any pointers?
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2005-05-03 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 10:56 Han-Wen Nienhuys [this message]
2005-05-04 18:22 ` Backtraces in modules? Andy Wingo
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=427758DC.1020107@xs4all.nl \
--to=hanwen@xs4all.nl \
/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).