From: William Morgan <wmorgan@masanjin.net>
Subject: Re: wrong-type-arg in scm_display_backtrace
Date: Tue, 7 Jan 2003 00:42:32 -0500 [thread overview]
Message-ID: <20030107054232.GA10760@masanjin.net> (raw)
In-Reply-To: <m3r8bqm72t.fsf@laruns.ossau.uklinux.net>
Excerpts (reformatted) from Neil Jerram's mail of 6 Jan 2003 (EST):
> I don't know; it looks OK to me.
Ok, it's good to know that I'm on the right track, at least.
> Perhaps you could try putting a breakpoint on ss_handler, where
> the-last-stack is set, then (assuming that setting makes it non-#f)
> step through from there to find out where it gets reset.
It seems as if scm_make_stack is always returning #f. In particular, the
code in throw.c :
static SCM
ss_handler (void *data SCM_UNUSED, SCM tag, SCM throw_args)
{
/* Save the stack */
scm_fluid_set_x (SCM_VARIABLE_REF (scm_the_last_stack_fluid_var),
scm_make_stack (SCM_BOOL_T, SCM_EOL));
always sets scm_the_last_stack_fluid_var to #f because of this. Why
would this be? I thought the whole point of lazy catches was to preserve
the call stack...
Anyways, I have looked at scm_make_stack briefly but haven't been able
to make head or tail of it yet.
> What is your Guile version, BTW?
I'm using 1.6.1. I have a small .c file that demonstrates this if you're
interested.
Thanks again for all of your help.
--
William <wmorgan@masanjin.net>
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-01-07 5:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 1:31 wrong-type-arg in scm_display_backtrace William Morgan
2002-12-31 23:42 ` Neil Jerram
2003-01-05 3:57 ` William Morgan
2003-01-06 19:06 ` Neil Jerram
2003-01-07 5:42 ` William Morgan [this message]
2003-01-08 20:21 ` Neil Jerram
2003-01-08 22:38 ` William Morgan
2003-01-09 23:42 ` Neil Jerram
2003-01-10 20:31 ` vports from c questions William Morgan
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=20030107054232.GA10760@masanjin.net \
--to=wmorgan@masanjin.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).