From: Stan Pinte <alto_stan@wanadoo.be>
Cc: guile-gtk@sources.redhat.com
Subject: Re: bug in threading implementation, using guile-1.6.1
Date: Tue, 31 Dec 2002 14:22:45 +0100 [thread overview]
Message-ID: <20021231142245.29817120.alto_stan@wanadoo.be> (raw)
In-Reply-To: <20021231134424.2faa08ad.alto_stan@wanadoo.be>
100% cpu is also the case with the
"--with-threads=coop" flag.
Stan
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2002-12-31 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 12:44 bug in threading implementation, using guile-1.6.1 Stan Pinte
2002-12-31 13:22 ` Stan Pinte [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=20021231142245.29817120.alto_stan@wanadoo.be \
--to=alto_stan@wanadoo.be \
--cc=guile-gtk@sources.redhat.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).