unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Ken Raeburn <raeburn@raeburn.org>
Cc: guile-devel@gnu.org
Subject: Re: deadlock in 1.7.91 ?
Date: Mon, 6 Mar 2006 14:57:37 -0500	[thread overview]
Message-ID: <7CB6664A-0650-4C8A-B753-641A967DCAF5@raeburn.org> (raw)
In-Reply-To: <20060306092721.GD28115@basalt.office.altlinux.org>

On Mar 6, 2006, at 4:27, Stanislav Ievlev wrote:
> On Sun, Feb 26, 2006 at 12:58:46PM +0300, Stanislav Ievlev wrote:
>> Hi!
>>
>> What about this problem?
> Problem was in hidden select in g_main_loop (thanks to myself)
>
> We really need enter_guile(), leave_guile() for such cases.
> with-guile/without-guile will not work.
>
> Are you planning to fix this problem?

But scm_leave_guile can result in garbage collection bugs in  
multithreaded programs.  Look in threads.c for a copy of the email  
message I wrote on the problem.  (There may be similar issues with  
scm_enter_guile, I haven't thought as hard about it.)  I doubt this  
can be fixed with that API, but if you spot something I missed, I'd  
be glad to hear about it.

The list archives seem to be missing some messages at the end of  
February.  Why will with/without-guile not work for you?  In the  
message dated 20 Feb in the archive, can you not call g_main_loop_run  
via scm_without_guile?

Ken


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


      reply	other threads:[~2006-03-06 19:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 13:33 deadlock in 1.7.91 ? Stanislav Ievlev
2006-02-26  9:58 ` Stanislav Ievlev
2006-03-06  9:27   ` Stanislav Ievlev
2006-03-06 19:57     ` Ken Raeburn [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=7CB6664A-0650-4C8A-B753-641A967DCAF5@raeburn.org \
    --to=raeburn@raeburn.org \
    --cc=guile-devel@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).