From: anonymous <INVALID.NOREPLY@gnu.org>
To: bug-guile@gnu.org
Subject: [bug #33498] Guile 2.0.1 segfaults on (begin-thread . . .
Date: Wed, 08 Jun 2011 18:56:43 +0000 [thread overview]
Message-ID: <20110608-185642.sv0.85262@savannah.gnu.org> (raw)
In-Reply-To:
URL:
<http://savannah.gnu.org/bugs/?33498>
Summary: Guile 2.0.1 segfaults on (begin-thread . . .
Project: Guile
Submitted by: None
Submitted on: Wed 08 Jun 2011 06:56:42 PM UTC
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
Any way I use (begin-thread . . .) I get a segfault. I may be using it
incorrectly, of course, but a segfault is probably not the best result.
==================================================
Here's a sample session:
GNU Guile 2.0.1
Copyright (C) 1995-2011 Free Software Foundation, Inc.
Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.
Enter `,help' for help.
scheme@(guile-user)> (begin-thread (display "test"))
test$1 =
Process scheme segmentation fault
==================================================
I'm happy to supply more information if needed.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?33498>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next reply other threads:[~2011-06-08 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 18:56 anonymous [this message]
2011-06-09 0:55 ` [bug #33498] Guile 2.0.1 segfaults on (begin-thread . . 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
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=20110608-185642.sv0.85262@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@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).