From: rixed@happyleptic.org
To: guile-user@gnu.org
Subject: Re: open-pipe deadlocked
Date: Fri, 2 Sep 2011 10:13:33 +0200 [thread overview]
Message-ID: <20110902081333.GA25610@ccellier.rd.securactive.lan> (raw)
In-Reply-To: <87d3fkc4xq.fsf@gnu.org>
-[ Thu, Sep 01, 2011 at 11:45:37PM +0200, Ludovic Courtès ]----
> Hi Cédric,
>
> rixed@happyleptic.org skribis:
>
> > I attached 2 files:
> >
> > - "guile deadlock.scm > /tmp/log" deadlocks after around 12k lines of output for me
>
> AFAICS the problem does not occur with Guile 2.0.
> For 1.8, could you try running Helgrind and see what happens?
Will do.
> > - more surprisingly, "guile crash.scm > /dev/log" segfaults with this
> > backtrace :
>
> Well yes, ports still aren???t thread-safe ;-) so this is bound to crash
> in unexpected ways.
>
> With Guile 2.0, it always ends up with:
>
> --8<---------------cut here---------------start------------->8---
> ERROR: In procedure display:
> ERROR: In procedure fport_write: Bad address
> --8<---------------cut here---------------end--------------->8---
With guile 2.0.2 it sometimes ends with this or sometime segfaults. See
the ticket I opened at savannah here for a backtrace:
https://savannah.gnu.org/bugs/?33996
next prev parent reply other threads:[~2011-09-02 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 13:56 open-pipe deadlocked rixed
2011-08-02 21:24 ` Andreas Rottmann
2011-08-04 7:18 ` rixed
2011-09-01 21:45 ` Ludovic Courtès
2011-09-02 8:13 ` rixed [this message]
2011-09-02 9:26 ` rixed
2011-09-02 10:58 ` rixed
2011-09-02 10:58 ` rixed
2011-09-03 20:32 ` Ludovic Courtès
2011-09-04 10:18 ` Andy Wingo
2011-09-05 7:30 ` rixed
2011-08-10 18:31 ` rixed
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=20110902081333.GA25610@ccellier.rd.securactive.lan \
--to=rixed@happyleptic.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).