data point, the bug only reproduces with address space
layout randomization enabled.
Do you have any idea what might be causing this? At LilyPond, we're
totally lost on what could provoke such an internal crash in BDWGC.
Do you have successful experience with using Guile 2.2 on Windows?
Did y
enabled. Do you have any idea what might be causing
this? At LilyPond, we're totally lost on what could provoke such an
internal crash in BDWGC. Do you have successful experience with using
Guile 2.2 on Windows? Did you see this kind of thing before? In short,
does it ring a bell? Thanks,
Hi Mark,
Thank you. A little while ago I sent an email off to libtool because
the actual command name was not set into a variable.
The command that failed was:
$to_tool_file_cmd "$1"
and the command trace leading up to it was:
> >lt-func_mode_compile> func_to_tool_file alloc.c func_convert_f
Bruce Korb writes:
> I cannot build Guile for OS/X without first building package after
> package after package after package.
> It goes on nearly forever. After going through 3 successful library
> builds and installs and 3 build tool
> builds and installs, I hit this bdwgc wall:
I cannot build Guile for OS/X without first building package after
package after package after package.
It goes on nearly forever. After going through 3 successful library
builds and installs and 3 build tool
builds and installs, I hit this bdwgc wall:
$ for t in autoconf automake libtool;do $t
le-2.0 are built and linked with bdwgc
> 7.2alpha from CVS, circa 2011-03-27. This on gNewSense metad/mipsel
> (slightly modified Debian Lenny).
Hi Mark,
Mark H Weaver writes:
> Sometime between 2.0.0 and current stable-2.0, after-gc-hook has been
> broken on my system: "FAIL: gc.test: gc: after-gc-hook gets called".
FWIW Hydra has had this problem in the GCC 3.x build job:
http://hydra.nixos.org/build/1043456
It first had the probl
On Sat 09 Apr 2011 07:05, Mark H Weaver writes:
> Sometime between 2.0.0 and current stable-2.0, after-gc-hook has been
> broken on my system: "FAIL: gc.test: gc: after-gc-hook gets called".
>
> Both 2.0.0 and current stable-2.0 are built and linked with bdwgc
> 7.2alph
Sometime between 2.0.0 and current stable-2.0, after-gc-hook has been
broken on my system: "FAIL: gc.test: gc: after-gc-hook gets called".
Both 2.0.0 and current stable-2.0 are built and linked with bdwgc
7.2alpha from CVS, circa 2011-03-27. This on gNewSense metad/mipsel
(slightl
