GNU logs - #33641, boring messages

Message sent to bug-guile@HIDDEN:

Subject: bug#33641: guile-2.9.1 multi-threading crash
Resent-From: Linas Vepstas <linasvepstas@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guile@HIDDEN
Resent-Date: Thu, 06 Dec 2018 02:42:01 +0000
Resent-Message-ID: <handler.33641.B.154406406527245 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 33641 <at> debbugs.gnu.org
Reply-To: linasvepstas@HIDDEN
MIME-Version: 1.0
From: Linas Vepstas <linasvepstas@HIDDEN>
Date: Wed, 5 Dec 2018 20:40:20 -0600
Message-ID: <CAHrUA37oy7NgytspabAPPCzZhbQLEHVZGL-EgYyJZbG+S0DkLQ@HIDDEN>
Content-Type: multipart/alternative; boundary="00000000000048672d057c516c22"
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

--00000000000048672d057c516c22
Content-Type: text/plain; charset="UTF-8"

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

--00000000000048672d057c516c22
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div><b=
r></div>The following bug report is informal, without any simple test, righ=
t now. Very reproducible, though. <br><br>I have a unit test (it passes wit=
h guile-2.2) that creates 120 threads and races them as fast as possible, e=
ach 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<br>```<br>(gdb) info threads<br>=C2=A0 Id=
=C2=A0=C2=A0 Target Id=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Fram=
e<br>=C2=A0 1=C2=A0=C2=A0=C2=A0 Thread 0x7ffff7fdcbc0 (LWP 24595) &quot;Mul=
tiThreadUTes&quot;<br>0x00007ffff7bc298d in pthread_join (threadid=3D140737=
247344384,<br>thread_return=3D0x0)<br>=C2=A0=C2=A0=C2=A0 at pthread_join.c:=
90<br>```<br>and most of the rest in `__lll_lock_wait` (that my c++ code as=
ks 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=3D0x0` above.=
<br>```<br>(gdb) bt<br>#0=C2=A0 0x00007ffdb03c7040 in ?? ()<br>#1=C2=A0 0x0=
000000000000001 in ?? ()<br>#2=C2=A0 0x00007ffff40a553c in __GI___libc_free=
 (mem=3D&lt;optimized out&gt;)<br>=C2=A0=C2=A0=C2=A0 at malloc.c:2968<br>#3=
=C2=A0 0x0000000000000000 in ?? ()<br>```<br>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.<br><br></div><div>(Reproducible by running th=
e &quot;MultiThreadUTest&quot; of <a href=3D"https://github.com/opencog/ato=
mspace">https://github.com/opencog/atomspace</a>)<br><br clear=3D"all"></di=
v><div dir=3D"ltr"><div>-- Linas<br></div><div>-- <br><div dir=3D"ltr" clas=
s=3D"gmail_signature"><div dir=3D"ltr">cassette tapes - analog TV - film ca=
meras - you<br></div></div></div></div></div></div></div>

--00000000000048672d057c516c22--

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: linasvepstas@HIDDEN
Subject: bug#33641: Acknowledgement (guile-2.9.1 multi-threading crash)
Message-ID: <handler.33641.B.154406406527245.ack <at> debbugs.gnu.org>
References: <CAHrUA37oy7NgytspabAPPCzZhbQLEHVZGL-EgYyJZbG+S0DkLQ@HIDDEN>
X-Gnu-PR-Message: ack 33641
X-Gnu-PR-Package: guile
Reply-To: 33641 <at> debbugs.gnu.org
Date: Thu, 06 Dec 2018 02:42:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-guile@HIDDEN

If you wish to submit further information on this problem, please
send it to 33641 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
33641: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D33641
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.