From: Andy Wingo <wingo@pobox.com>
To: primus <rprimus@gmail.com>
Cc: bug-guile@gnu.org
Subject: Re: [1.9.12] Abort trap error ...
Date: Sun, 27 Feb 2011 21:55:11 +0100 [thread overview]
Message-ID: <m3wrklryds.fsf@unquote.localdomain> (raw)
In-Reply-To: <20101115212715.GG28907@x.lence.net> (primus's message of "Mon, 15 Nov 2010 21:27:15 +0000")
On Mon 15 Nov 2010 22:27, primus <rprimus@gmail.com> writes:
>> On Tue 14 Sep 2010 12:36, primus <rprimus@gmail.com> writes:
>>
>> > Enter `,help' for help.
>> > scheme@(guile-user)> (define one 1)
>> > GC_push_all_stacks: sp not set!
>> > Abort trap
>>
> To get guile to compile I installed the latest
> (CVS) version of GC: 7.2.5
>
> I've not been able to work around it.
I assume this is still the case. Can you get a backtrace from all
threads in GDB: "thr apply all bt full" -- and send to the list?
Ideally with -O0.
Thanks,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-02-27 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 10:36 [1.9.12] Abort trap error primus
2010-11-15 21:12 ` Andy Wingo
2010-11-15 21:27 ` primus
2011-02-27 20:55 ` 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=m3wrklryds.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=rprimus@gmail.com \
/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).