From: ludo@gnu.org (Ludovic Courtès)
To: Bruno Haible <bruno@clisp.org>
Cc: 10520-done@debbugs.gnu.org
Subject: bug#10520: [platform-testers] Guile 2.0.4 release imminent
Date: Tue, 24 Jan 2012 23:53:35 +0100 [thread overview]
Message-ID: <87hazkpv9s.fsf@gnu.org> (raw)
In-Reply-To: <87y5t1cl3e.fsf@gnu.org> ("Ludovic \=\?iso-8859-1\?Q\?Court\=E8s\?\= \=\?iso-8859-1\?Q\?\=22's\?\= message of "Sat, 21 Jan 2012 13:10:29 +0100")
Hi Bruno,
ludo@gnu.org (Ludovic Courtès) skribis:
> Bruno Haible <bruno@clisp.org> skribis:
>
>> 8) On Linux/hppa and Linux/SPARC32 and Linux/IA-64, build failure in the
>> libguile directory:
>>
>> SNARF socket.doc
>> SNARF regex-posix.doc
>> GEN guile-procedures.texi
>> /bin/sh: line 1: 1022 Broken pipe cat alist.doc arbiters.doc array-handle.doc array-map.doc arrays.doc async.doc backtrace.doc boolean.doc bitvectors.doc bytevectors.doc chars.doc control.doc continuations.doc debug.doc deprecated.doc deprecation.doc dynl.doc dynwind.doc eq.doc error.doc eval.doc evalext.doc expand.doc extensions.doc feature.doc filesys.doc fluids.doc foreign.doc fports.doc gc-malloc.doc gc.doc gettext.doc generalized-arrays.doc generalized-vectors.doc goops.doc gsubr.doc guardians.doc hash.doc hashtab.doc hooks.doc i18n.doc init.doc ioext.doc keywords.doc list.doc load.doc macros.doc mallocs.doc memoize.doc modules.doc numbers.doc objprop.doc options.doc pairs.doc ports.doc print.doc procprop.doc procs.doc promises.doc r6rs-ports.doc random.doc rdelim.doc read.doc root.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc srcprop.doc srfi-1.doc srfi-4.doc srfi-13.doc srfi-14.doc srfi-60.doc stackchk.doc stacks.doc stime.doc strings.doc strorder.doc strports.doc struct.doc symbols.doc threads.doc throw.doc trees.doc uniform.doc values.doc variable.doc vectors.doc version.doc vports.doc weaks.doc dynl.doc posix.doc net_db.doc socket.doc regex-posix.doc
>> 1023 Segmentation fault | GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guild snarf-check-and-output-texi > guile-procedures.texi
>> make[3]: *** [guile-procedures.texi] Error 1
>
> I bisected this and found this harmless-looking patch to be the culprit:
>
> http://git.savannah.gnu.org/cgit/guile.git/commit/?id=3e54fdfc217969abb50a46ec9c9c5c02a2c7d369
>
> The segfault would occur in vm-i-system.c:1281, in the ‘CACHE_PROGRAM’
> macro, while trying to access ‘SCM_PROGRAM_DATA’, because of a bogus
> value for ‘program’, stemming from a bogus ‘fp’.
>
> After a long and tiring period of investigation, I found that reverting
> just the definitions SCM_FRAME_DYNAMIC_LINK and
> SCM_FRAME_SET_DYNAMIC_LINK would solve the problem.
>
> Eventually, I found that, keeping frames.h unchanged, adding a compiler
> barrier after each ‘fp’ assignment would solve the problem:
I’ve checked this in:
http://git.sv.gnu.org/cgit/guile.git/commit/?h=stable-2.0&id=2b264d7e4fb649955ade1814527b6eb6f34f4e18
Closing the bug, because I think bugs were all addressed. Let us know
if you think I got it wrong!
Thanks,
Ludo’.
next prev parent reply other threads:[~2012-01-24 22:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87boq6qnel.fsf@gnu.org>
2012-01-16 1:38 ` bug#10520: [platform-testers] Guile 2.0.4 release imminent Bruno Haible
2012-01-16 1:54 ` Bruno Haible
2012-01-16 23:43 ` Ludovic Courtès
2012-01-16 23:44 ` Bruno Haible
2012-01-16 23:08 ` Ludovic Courtès
2012-01-17 0:22 ` Bruno Haible
2012-01-17 15:01 ` Ludovic Courtès
2012-01-21 12:10 ` Ludovic Courtès
2012-01-24 22:53 ` Ludovic Courtès [this message]
2012-01-29 21:24 ` Ludovic Courtès
2012-01-21 12:13 ` bug#10520: Status: " Ludovic Courtès
2012-01-19 3:29 ` bug#10553: " David Fang
2012-02-03 14:44 ` Andy Wingo
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=87hazkpv9s.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=10520-done@debbugs.gnu.org \
--cc=bruno@clisp.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).