From: Andy Wingo <wingo@pobox.com>
To: "Carroll-Nellenback\, Jonathan" <jonathan.carroll@rochester.edu>
Cc: 15838-done@debbugs.gnu.org,
Research Computing <researchcomputing@rochester.edu>
Subject: bug#15838: Guile 2.0.9 on BlueGene Q
Date: Tue, 21 Jun 2016 14:03:17 +0200 [thread overview]
Message-ID: <8760t221h6.fsf@pobox.com> (raw)
In-Reply-To: <CEA2C3EF.1A103%jcarrol5@ur.rochester.edu> (Jonathan Carroll-Nellenback's message of "Fri, 8 Nov 2013 21:39:01 +0000")
Hi Jonathan,
Thanks for the report and sorry for never getting back to you. The good
news is that there are new releases of Guile and libgc. The bad news is
that we can't do anything for you on this report, given that there are
new releases and there's not much other info. I know you've probably
moved on, but apologies in any case. Please open a new bug if you have
build or run errors on Guile 2.0.11 with the latest stable libgc.
Cheers,
Andy
On Fri 08 Nov 2013 22:39, "Carroll-Nellenback, Jonathan" <jonathan.carroll@rochester.edu> writes:
> Hi,
> I am trying to run guile 2.0.9 on the BlueGene Q architecture, but
> when I try to run the following guile script,
>
> (display "Hello, world!")
> (newline)
>
> the code exits immediately with the following error:
>
> *** glibc detected *** /usr/local/guile/2.0.9/bin/guile: free():
> invalid next size (fast): 0x00000019c6001f00 ***
>
> I’ve been able to build and run it successfully on the head nodes -
> but when I cross compile for the compute nodes, the code dies.
>
> I’ve attached the config.log and the output from make and here is the
> backtrace
>
> /bgsys/drivers/V1R2M0/ppc64/toolchain/gnu/glibc-2.12.2/stdlib/abort.c:77
> /bgsys/drivers/V1R2M0/ppc64/toolchain/gnu/glibc-2.12.2/libio/../sysdeps/unix/sysv/linux/libc_fatal.c:186
> /bgsys/drivers/V1R2M0/ppc64/toolchain/gnu/glibc-2.12.2/malloc/malloc.c:6327
> /bgsys/drivers/V1R2M0/ppc64/toolchain/gnu/glibc-2.12.2/malloc/malloc.c:3779
> /bgsys/drivers/V1R2M0/ppc64/toolchain/gnu/glibc-2.12.2/nptl/pthread_attr_destroy.c:42
> :0
> :0
> /usr/local/src/guile/guile-2.0.9/libguile/gc.c:653
> /usr/local/src/guile/guile-2.0.9/libguile/init.c:385
> /usr/local/src/guile/guile-2.0.9/libguile/threads.c:835
> /usr/local/src/guile/guile-2.0.9/libguile/threads.c:901
> :0
> /usr/local/src/guile/guile-2.0.9/libguile/threads.c:951
> /usr/local/src/guile/guile-2.0.9/libguile/threads.c:957
> /usr/local/src/guile/guile-2.0.9/libguile/init.c:320
> /usr/local/src/guile/guile-2.0.9/libguile/guile.c:108
> /bgsys/drivers/V1R2M0/ppc64/toolchain/gnu/glibc-2.12.2/csu/../csu/libc-start.c:226
> /bgsys/drivers/V1R2M0/ppc64/toolchain/gnu/glibc-2.12.2/csu/../sysdeps/unix/sysv/linux/powerpc/libc-start.c:194
> ??:0
prev parent reply other threads:[~2016-06-21 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 21:39 bug#15838: Guile 2.0.9 on BlueGene Q Carroll-Nellenback, Jonathan
2016-06-21 12:03 ` Andy Wingo [this message]
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=8760t221h6.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=15838-done@debbugs.gnu.org \
--cc=jonathan.carroll@rochester.edu \
--cc=researchcomputing@rochester.edu \
/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).