From: Linas Vepstas <INVALID.NOREPLY@gnu.org>
To: "Andy Wingo" <wingo@pobox.com>, "Ludovic Courtès" <ludo@gnu.org>,
"Linas Vepstas" <linasvepstas@gmail.com>,
bug-guile@gnu.org
Subject: [bug #24867] `define' should be thread-safe
Date: Tue, 23 Dec 2008 03:06:42 +0000 [thread overview]
Message-ID: <20081223-030642.sv71519.76086@savannah.gnu.org> (raw)
In-Reply-To: <20081223-025008.sv71519.28260@savannah.gnu.org>
Follow-up Comment #3, bug #24867 (project guile):
Note that the attached test case shows 4 distinct behaviours:
1) runs fine, exiting normally, w/o any errors
2) Spewing messages such as:
ERROR: Unbound variable: x2-347
ERROR: Unbound variable: x2-347
ERROR: Unbound variable: x2-347
ERROR: Unbound variable: define
ERROR: Unbound variable: x1-2525
ERROR: Unbound variable: x1-2525
ERROR: Unbound variable: x1-2525
ERROR: Unbound variable: x1-2525
ERROR: Unbound variable: x1-2525
ERROR: Unbound variable: x1-2525
the numbers being different each time, of course, but then exiting
normally.
3) Deadlocking in garbage collection, with all four threads
stuck in
#5 0xf7f01f6b in scm_gc_for_newcell (freelist=0xf7f8c8ec,
free_cells=0x90c810c) at gc.c:484
(this may be preceeded by the prints above)
4) Segfault:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xf74c5b90 (LWP 30649)]
0xf7f426ad in scm_assert_smob_type (tag=639, val=0x0) at smob.c:63
63 if (!SCM_SMOB_PREDICATE (tag, val))
(gdb) bt
#0 0xf7f426ad in scm_assert_smob_type (tag=639, val=0x0) at smob.c:63
#1 0xf7f0b4c5 in scm_make_dynamic_state (parent=0x0) at fluids.c:508
#2 0xf7f62bdf in guilify_self_2 (parent=0x0) at threads.c:508
#3 0xf7f64992 in scm_i_init_thread_for_guile (base=0xf74c5388, parent=0x0)
at threads.c:611
#4 0xf7f649c5 in scm_i_with_guile_and_parent (
func=0x8048754 <guile_mode_definer>, data=0xffaf0cbc, parent=0x0)
at threads.c:743
#5 0xf7f64ace in scm_with_guile (func=0x8048754 <guile_mode_definer>,
data=0xffaf0cbc) at threads.c:732
#6 0x080488a8 in definer ()
#7 0xf7fa14fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8 0xf7e45e5e in clone () from /lib/tls/i686/cmov/libc.so.6
I'm guessing that the use of immutable vlists, as proposed by Ludo, for use
in the module-obarray per mail discussion, would solve all of the above.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?24867>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2008-12-23 3:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 10:18 [bug #24867] `define' should be thread-safe Ludovic Courtès
2008-11-18 13:27 ` Ludovic Courtès
2008-12-23 2:36 ` Linas Vepstas
2008-12-23 2:50 ` Linas Vepstas
2008-12-23 3:06 ` Linas Vepstas [this message]
2008-12-23 15:21 ` Ludovic Courtès
2008-12-23 18:28 ` Linas Vepstas
2008-12-23 19:10 ` Linas Vepstas
2010-09-20 9:28 ` Kourtney Keese
2011-08-06 9:08 ` JackBenny
2011-08-06 9:08 ` JackBenny
2011-08-06 9:09 ` JackBenny
2011-08-06 9:09 ` JackBenny
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=20081223-030642.sv71519.76086@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=linasvepstas@gmail.com \
--cc=ludo@gnu.org \
--cc=wingo@pobox.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).