From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: built with SCM_DEBUG=1 lately?
Date: Tue, 12 Jul 2005 10:53:46 +1000 [thread overview]
Message-ID: <87pstorgit.fsf@zip.com.au> (raw)
In-Reply-To: tx14qbf9g9s.fsf@raeburn.org
Ken Raeburn <raeburn@raeburn.org> writes:
>
> From the comments, it looks like the list returned by scm_i_dynwinds
> can have both cons cells and smob objects in it, like the winder
> object that was keeping the snarf step from working for me.
Yep that happens for me too, though it seems to have been non-fatal
(in a non-debug build). Dunno what's meant to happen though.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-07-12 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 6:44 built with SCM_DEBUG=1 lately? Ken Raeburn
2005-07-12 0:53 ` Kevin Ryde [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-01 6:18 Ken Raeburn
2005-07-11 23:55 ` Kevin Ryde
2005-06-24 2:50 Ken Raeburn
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=87pstorgit.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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).