From: Ken Raeburn <raeburn@gnu.org>
Subject: built with SCM_DEBUG=1 lately?
Date: Thu, 23 Jun 2005 22:50:42 -0400 [thread overview]
Message-ID: <c7a991e8d0a79d4754e7093b938400ca@gnu.org> (raw)
I was running into some problems with free() reporting unaligned
pointers on my mac laptop, and decided to try switching on more
debugging options. I tried building with SCM_DEBUG=1, and several
files needed tweaking. Mostly in minor ways, due to -Werror -- %d for
long values, stuff like that. I'll send out a patch soon.
But after I got guile building again, it died with this error in the
snarf step (first message is my added instrumentation).
../../source/libguile/throw.c:626: non-pair accessed with SCM_CDR:
x=312960 x->car=50d7f
Non-pair accessed with SCM_C[AD]R: `#<winder 312960>?
for (wind_goal = scm_i_dynwinds ();
!scm_is_eq (SCM_CDAR (wind_goal), jmpbuf); <<<----
wind_goal = SCM_CDR (wind_goal))
;
So it's got a cons cell, but the car of the cons cell is not a plain
cons cell but a "winder" smob object. Perhaps the equivalent of
WINDER_PROC or WINDER_DATA is what's desired here?
Ken
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2005-06-24 2:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 2:50 Ken Raeburn [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-01 6:18 built with SCM_DEBUG=1 lately? Ken Raeburn
2005-07-11 23:55 ` Kevin Ryde
2005-07-01 6:44 Ken Raeburn
2005-07-12 0:53 ` Kevin Ryde
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=c7a991e8d0a79d4754e7093b938400ca@gnu.org \
--to=raeburn@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).