From: Marijn <hkBst@gentoo.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guile@gnu.org
Subject: Re: guile-2.0.0 fails to build without threads
Date: Tue, 03 May 2011 16:58:17 +0200 [thread overview]
Message-ID: <4DC01809.1090704@gentoo.org> (raw)
In-Reply-To: <87k4ee8lad.fsf@gnu.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/28/11 17:09, Ludovic Courtès wrote:
> Andy Wingo <wingo@pobox.com> writes:
>
>> On Thu 28 Apr 2011 15:08, ludo@gnu.org (Ludovic Courtès) writes:
>>
>>>> /* Sanity check. */
>>>> if (!GC_is_visible (&scm_protects))
>>>> abort ();
>>
>> Is this even the right check to make?
>
> Yes: the goal is to make sure that the ‘scm_protect’ variable itself is
> a GC root.
>
> Actually, Marijn: can you try “GC_DUMP_REGULARLY=1 ./meta/guile -c 0”,
> and check what’s under “Static roots”?
Current stable-2.0 fails with:
GEN guile-procedures.texi
0x75b320 is not a GC visible pointer location
GC_is_visible test failed
requested output:
***Static roots:
- From 0x601000 to 0x6010c0 (temporary)
- From 0x7f79a7ab9000 to 0x7f79a7abb5c8 (temporary)
- From 0x7f79a787c000 to 0x7f79a78a8bb8 (temporary)
- From 0x7f79a7527000 to 0x7f79a752c8a8 (temporary)
- From 0x7f79a71a5000 to 0x7f79a71a5100 (temporary)
- From 0x7f79a6f60000 to 0x7f79a6fa1fe0 (temporary)
- From 0x7f79a6d3d000 to 0x7f79a6d3d5f0 (temporary)
- From 0x7f79a6b34000 to 0x7f79a6b35868 (temporary)
- From 0x7f79a6814000 to 0x7f79a681c140 (temporary)
- From 0x7f79a65ac000 to 0x7f79a65ac2b0 (temporary)
- From 0x7f79a6374000 to 0x7f79a63a21c0 (temporary)
- From 0x7f79a616b000 to 0x7f79a616b0e8 (temporary)
- From 0x7f79a7cdb000 to 0x7f79a7cdc188 (temporary)
Total size: 721472
> Thanks,
> Ludo’.
You're welcome and thanks for looking into this,
Marijn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3AGAkACgkQp/VmCx0OL2zJ7ACeNTKDiDBDKuz3kb6Xp5Ql3fx1
l1AAn3w3mdrzNfhYO72dM8dNHlLrnI+g
=BJor
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-05-03 14:58 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 14:47 guile-2.0.0 fails to build without threads Marijn
2011-04-11 16:19 ` Andy Wingo
2011-04-12 7:26 ` Marijn
2011-04-13 10:05 ` Andy Wingo
2011-04-13 13:44 ` Marijn
2011-04-13 14:09 ` Andy Wingo
2011-04-13 14:27 ` Marijn
2011-04-13 15:22 ` Andy Wingo
2011-04-14 13:25 ` Marijn
2011-04-28 11:17 ` Andy Wingo
2011-04-28 13:08 ` Ludovic Courtès
2011-04-28 13:15 ` Andy Wingo
2011-04-28 15:09 ` Ludovic Courtès
2011-05-03 14:58 ` Marijn [this message]
2011-05-04 12:19 ` Ludovic Courtès
2011-05-05 8:04 ` Marijn
2011-05-05 12:08 ` Ludovic Courtès
2011-05-05 13:59 ` Marijn
2011-05-05 14:25 ` Ludovic Courtès
2011-05-06 8:16 ` Marijn
2011-05-06 9:52 ` Ludovic Courtès
2011-05-06 12:49 ` Marijn
2011-05-10 7:43 ` Marijn
2011-05-03 14:55 ` Marijn
2011-04-12 6:49 ` Marco Maggi
2011-04-13 9:04 ` Marco Maggi
2011-04-13 11:42 ` Marco Maggi
2011-04-13 12:26 ` Andy Wingo
2011-04-13 13:56 ` Marco Maggi
2011-04-28 11:21 ` Andy Wingo
2011-05-02 6:20 ` Marco Maggi
2011-05-20 9:37 ` Andy Wingo
2011-05-20 18:41 ` Marco Maggi
2011-05-21 2:23 ` Mark H Weaver
2011-05-21 8:45 ` Andy Wingo
2011-05-21 13:51 ` Marco Maggi
2011-05-21 14:29 ` Neil Jerram
2011-06-17 10:25 ` Andy Wingo
2011-06-20 8:06 ` Andy Wingo
2011-06-22 21:39 ` Neil Jerram
2011-04-13 9:55 ` Andy Wingo
2011-04-13 14:19 ` Marco Maggi
2011-04-13 21:57 ` 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=4DC01809.1090704@gentoo.org \
--to=hkbst@gentoo.org \
--cc=bug-guile@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).