From: Andy Wingo <wingo@pobox.com>
To: "Germán A. Arias" <german@xelalug.org>
Cc: Guile <guile-user@gnu.org>
Subject: Re: guile-lib test failed
Date: Mon, 21 May 2012 11:05:05 +0200 [thread overview]
Message-ID: <87txz9zyym.fsf@pobox.com> (raw)
In-Reply-To: <20120520063150.524acb49@rafaela> ("Germán A. Arias"'s message of "Sun, 20 May 2012 06:31:50 -0600")
On Sun 20 May 2012 14:31, "Germán A. Arias" <german@xelalug.org> writes:
> /bin/sh: lÃnea 5: 9636 Violacion de segmento API_FILE=./guile-library.api DOC_GUILE_LIBRARY_SCM=../doc/guile-library.scm GUILE_AUTO_COMPILE=0 ../dev-environ /usr/local/bin/guile -s ${dir}$tst
> FAIL: container.async-queue.scm
A segmentation fault! This is bad.
Can you run "ulimit -c unlimited" to enable core dumps, then try again,
then "gdb /usr/local/bin/guile core" (assuming the core file is there;
if not, check your /proc/sys/kernel/core_pattern), then "thr apply all
bt full".
Thanks!
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2012-05-21 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 12:31 guile-lib test failed Germán A. Arias
2012-05-21 9:05 ` 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=87txz9zyym.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=german@xelalug.org \
--cc=guile-user@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).