unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Linas Vepstas" <linasvepstas@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: [PATCH]: Critical section checked for incorrect thread.
Date: Sat, 13 Dec 2008 17:39:08 -0600	[thread overview]
Message-ID: <3ae3aa420812131539v7eb5e53dp65cb12d2dc67cc18@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]

The patch below was previously submitted:
http://www.mail-archive.com/bug-guile@gnu.org/msg04618.html
but was never applied, I don't know why; there was no
'yea' or 'nay' response.  Please apply; this provides at
least some stability for multi-threaded operation.

--linas

At any given time, some thread might be in a critical section.
Some other thread may be throwing an error for some utterly
unrelated reason.  Yet, when the error is thrown, the
"critical section" check will trip, and it will do so for an
utterly bogus reason. This patch performs the critical section
check, for only for the current thread.

Signed-off-by: Linas Vepstas <linasvepstas@gmail.com>

---
 libguile/throw.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: guile-1.8.6/libguile/throw.c
===================================================================
--- guile-1.8.6.orig/libguile/throw.c  2008-12-08 11:42:56.000000000 -0600
+++ guile-1.8.6/libguile/throw.c 2008-12-13 17:28:27.000000000 -0600
@@ -692,7 +692,7 @@ scm_ithrow (SCM key, SCM args, int noret
   SCM dynpair = SCM_UNDEFINED;
   SCM winds;

-  if (scm_i_critical_section_level)
+  if (SCM_I_CURRENT_THREAD->block_asyncs)
     {
       fprintf (stderr, "throw from within critical section.\n");
       abort ();

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: crit-section.patch --]
[-- Type: text/x-diff; name=crit-section.patch, Size: 1210 bytes --]

Date: 13 Nov 2008
To: guile-devel@gnu.org
Subject: Re: Does anyone actually use threads with guile?

Missed 1.8.6, resubmit on 13 Dec 2008
Subject: [PATCH]: Critical section checked for incorrect thread.

At any given time, some thread might be in a critical section. 
Some other thread may be throwing an error for some utterly
unrelated reason.  Yet, when the error is thrown, the 
"critical section" check will trip, and it will do so for an
utterly bogus reason. This patch performs the critical section
check, for only for the current thread.

Signed-off-by: Linas Vepstas <linasvepstas@gmail.com>

---
 libguile/throw.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: guile-1.8.6/libguile/throw.c
===================================================================
--- guile-1.8.6.orig/libguile/throw.c	2008-12-08 11:42:56.000000000 -0600
+++ guile-1.8.6/libguile/throw.c	2008-12-13 17:28:27.000000000 -0600
@@ -692,7 +692,7 @@ scm_ithrow (SCM key, SCM args, int noret
   SCM dynpair = SCM_UNDEFINED;
   SCM winds;
 
-  if (scm_i_critical_section_level)
+  if (SCM_I_CURRENT_THREAD->block_asyncs)
     {
       fprintf (stderr, "throw from within critical section.\n");
       abort ();

             reply	other threads:[~2008-12-13 23:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-13 23:39 Linas Vepstas [this message]
2008-12-13 23:59 ` [PATCH]: Critical section checked for incorrect thread Ludovic Courtès
2008-12-16 22:21   ` 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=3ae3aa420812131539v7eb5e53dp65cb12d2dc67cc18@mail.gmail.com \
    --to=linasvepstas@gmail.com \
    --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).