From: Ken Raeburn <raeburn@raeburn.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: compiling with -DSCM_DEBUG=1
Date: Wed, 9 Sep 2009 11:51:24 -0400 [thread overview]
Message-ID: <B0716D8A-E0FE-48A7-8F17-A8C84FA67EA5@raeburn.org> (raw)
In-Reply-To: <87my57m7n2.fsf@gnu.org>
On Sep 7, 2009, at 05:22, Ludovic Courtès wrote:
>> Non-pair accessed with SCM_C[AD]R: `ERROR: In procedure symbol-
>> >string:
>> ERROR: Wrong type argument in position 1 (expecting symbol):
>> #<guardian 124e300 (reachable: 15 unreachable: 1)>
>
> Does that mean it’s this whole string that’s accessed with SCM_C[AD]R?
I'm not sure... it should be printing a value after the quote; I guess
it's encountering an error trying to print, as well.
>> I use a modified scm_error_pair_access() that prints the function's
>> name (as seen above)
>
> Hmm, I don’t see the function name, except ‘symbol->string’ above, but
> I’d expect it to be part of the string that’s accessed as a pair.
Sorry, I meant scm_error_pair_access() prints out
"scm_error_pair_access" to let me know it's been called.
> I cannot reproduce it here without SCM_DEBUG but with this simple
> patch
> instead:
> Any hints?
I would think that would do it, but I'm not seeing it either. Still
looking...
(BTW, for SCM_DEBUG=1 I also had to comment out a debugging check
using SCM_GC_MARK_P in gc.c, since the macro doesn't exist any more.)
Ken
next prev parent reply other threads:[~2009-09-09 15:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 2:06 compiling with -DSCM_DEBUG=1 Ken Raeburn
2009-09-01 19:35 ` Ludovic Courtès
2009-09-03 21:04 ` Ken Raeburn
2009-09-04 22:56 ` Ken Raeburn
2009-09-05 23:42 ` Ken Raeburn
2009-09-06 0:37 ` Ken Raeburn
2009-09-06 8:47 ` Andy Wingo
2009-09-07 9:22 ` Ludovic Courtès
2009-09-09 15:51 ` Ken Raeburn [this message]
2009-10-18 22:44 ` Neil Jerram
2009-10-19 13:52 ` Ken Raeburn
2009-10-19 18:47 ` Andy Wingo
2009-10-29 22:16 ` Ken Raeburn
2009-10-30 21:28 ` Neil Jerram
2009-10-31 15:42 ` Neil Jerram
2009-11-14 11:46 ` Andy Wingo
2009-11-14 13:47 ` Neil Jerram
2009-11-14 17:07 ` Ken Raeburn
2009-11-15 4:34 ` Ken Raeburn
2009-11-15 22:25 ` Neil Jerram
2009-11-16 6:08 ` Ken Raeburn
2009-11-16 19:27 ` Andy Wingo
2009-11-16 19:37 ` Ken Raeburn
2009-11-16 20:40 ` Neil Jerram
2009-11-15 22:10 ` Neil Jerram
2009-10-31 14:39 ` Ludovic Courtès
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=B0716D8A-E0FE-48A7-8F17-A8C84FA67EA5@raeburn.org \
--to=raeburn@raeburn.org \
--cc=guile-devel@gnu.org \
--cc=ludo@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).