From: Linas Vepstas <linasvepstas@gmail.com>
To: 33641@debbugs.gnu.org
Subject: bug#33641: guile-2.9.1 multi-threading crash
Date: Wed, 5 Dec 2018 20:40:20 -0600 [thread overview]
Message-ID: <CAHrUA37oy7NgytspabAPPCzZhbQLEHVZGL-EgYyJZbG+S0DkLQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
The following bug report is informal, without any simple test, right now.
Very reproducible, though.
I have a unit test (it passes with guile-2.2) that creates 120 threads and
races them as fast as possible, each thread launched from C++, entering
guile, and then from guile, calling some wrappered C++ code. With 2.9.1,
the test crashes about half the time, always with the same stack trace
```
(gdb) info threads
Id Target Id Frame
1 Thread 0x7ffff7fdcbc0 (LWP 24595) "MultiThreadUTes"
0x00007ffff7bc298d in pthread_join (threadid=140737247344384,
thread_return=0x0)
at pthread_join.c:90
```
and most of the rest in `__lll_lock_wait` (that my c++ code asks for) or
`pthread_cond_wait@@GLIBC_2.3.2` from GC_wait_marker. The stack trace
itself is useless; the core issue is the `thread_return=0x0` above.
```
(gdb) bt
#0 0x00007ffdb03c7040 in ?? ()
#1 0x0000000000000001 in ?? ()
#2 0x00007ffff40a553c in __GI___libc_free (mem=<optimized out>)
at malloc.c:2968
#3 0x0000000000000000 in ?? ()
```
Its hard to see what this has to do with guile, other than that this test
has been run thousands of times on guile-2.2 without issues.
(Reproducible by running the "MultiThreadUTest" of
https://github.com/opencog/atomspace)
-- Linas
--
cassette tapes - analog TV - film cameras - you
[-- Attachment #2: Type: text/html, Size: 1730 bytes --]
reply other threads:[~2018-12-06 2:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHrUA37oy7NgytspabAPPCzZhbQLEHVZGL-EgYyJZbG+S0DkLQ@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=33641@debbugs.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).