From: Andy Wingo <INVALID.NOREPLY@gnu.org>
To: Andy Wingo <wingo@pobox.com>,
"Jason R. Fruit" <JasonFruit@gmail.com>,
bug-guile@gnu.org
Subject: [bug #33498] Guile 2.0.1 segfaults on (begin-thread . . .
Date: Sun, 19 Jun 2011 20:20:15 +0000 [thread overview]
Message-ID: <20110619-202015.sv20118.85016@savannah.gnu.org> (raw)
In-Reply-To: <20110619-001559.sv83176.26834@savannah.gnu.org>
Follow-up Comment #5, bug #33498 (project guile):
Thanks for the info. Can you get a backtrace with gc 6.8? See
http://www.gnu.org/software/guile/manual/html_node/Reporting-Bugs.html#Reporting-Bugs
for instructions, but instead of "backtrace", enter "thread apply all
backtrace". Thanks!
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?33498>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
prev parent reply other threads:[~2011-06-19 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 18:56 [bug #33498] Guile 2.0.1 segfaults on (begin-thread . . anonymous
2011-06-09 0:55 ` Jason R. Fruit
2011-06-17 18:21 ` Andy Wingo
2011-06-19 0:14 ` Jason R. Fruit
2011-06-19 0:15 ` Jason R. Fruit
2011-06-19 20:20 ` 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=20110619-202015.sv20118.85016@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=JasonFruit@gmail.com \
--cc=bug-guile@gnu.org \
--cc=wingo@pobox.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).