From: Andy Wingo <wingo@pobox.com>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: compiling with -DSCM_DEBUG=1
Date: Sun, 06 Sep 2009 10:47:06 +0200 [thread overview]
Message-ID: <m3k50ciho5.fsf@pobox.com> (raw)
In-Reply-To: <57660D04-1760-48E5-BA55-74321E89D654@raeburn.org> (Ken Raeburn's message of "Sat, 5 Sep 2009 20:37:48 -0400")
On Sun 06 Sep 2009 02:37, Ken Raeburn <raeburn@raeburn.org> writes:
> BTW, the bdw-gc branch with my patch and SCM_DEBUG==1 still fails tests
> on my Mac.
>
> In guardians.c, line 169, SCM_CAR is applied to a non-pair:
>
> Running popen.test
> Running ports.test
>
> scm_error_pair_access
> 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)>
> FAIL: check-guile
>
> I use a modified scm_error_pair_access() that prints the function's name
> (as seen above) and then sleeps a while, so I can attach gdb and get
> this stack trace before letting it resume:
>
> #0 0x9487546e in __semwait_signal ()
> #1 0x948752ef in nanosleep$UNIX2003 ()
> #2 0x948cae71 in sleep$UNIX2003 ()
> #3 0x002ea943 in scm_error_pair_access (non_pair=0x11d9180) at ../../
> libguile/pairs.c:50
> #4 0x002c8e35 in finalize_guarded (ptr=0x11d91f0,
> finalizer_data=0x11d9188) at ../../libguile/guardians.c:169
> #5 0x000a0866 in GC_invoke_finalizers ()
> #6 0x000a2ce9 in GC_generic_malloc_many ()
> #7 0x000ab01a in GC_malloc ()
> #8 0x002ea987 in scm_cell [inlined] () at inline.h:66
> #9 0x002ea987 in scm_cons (x=0x9487546e, y=0x9487546e) at ../../
> libguile/pairs.c:66
> #10 0x002d0f5a in scm_make_list (n=0x4, init=0xb2920) at ../../
> libguile/list.c:121
> #11 0x002c8bbc in finalize_guarded (ptr=0x12615e8,
> finalizer_data=0x12615a0) at ../../libguile/guardians.c:125
> #12 0x000a0866 in GC_invoke_finalizers ()
Thanks for catching this bug. I'm sure Ludovic will look into it. We
should not release a 1.9.3 with bugs like this one.
A
--
http://wingolog.org/
next prev parent reply other threads:[~2009-09-06 8:47 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 [this message]
2009-09-07 9:22 ` Ludovic Courtès
2009-09-09 15:51 ` Ken Raeburn
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=m3k50ciho5.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=raeburn@raeburn.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).