pthread pthread_attr_setdetachstate crash

[kallisti5]

​http://sourceforge.net/projects/posixtest/files/posixtest/posixtestsuite-1.5.2/

• gcc -I./include ./conformance/interfaces/pthread_attr_setdetachstate/2-1.c -g
• LD_PRELOAD=libroot_debug.so ./a.out

KERN: 30030: DEBUGGER: _numBlocks > 0
KERN: debug_server: Thread 30030 entered the debugger: Debugger call: `_numBlocks > 0'
KERN: stack trace, current PC 0x1d3a70d4fc9  _kern_debugger + 0x9:
KERN:   (0x7f1f9b181360)  0x1d3a7178f5e  _ZN8BPrivate11processHeap4freeEPv + 0x18e
KERN:   (0x7f1f9b1813a0)  0x1d3a7179aa0  free + 0x40
KERN:   (0x7f1f9b1813c0)  0x1d3a70e2598  pthread_join + 0x88
KERN:   (0x7f1f9b181400)  0x13d1368dc42  main + 0x9d
KERN:   (0x7f1f9b181430)  0x13d1368dac1  _start + 0x51
KERN:   (0x7f1f9b181460)  0x7977d707e3  runtime_loader + 0xf3
KERN: debug_server: Killing team 30030 (./a.out)
KERN: debug_server: TeamDebugHandler::Init(): Failed to get info for team 30030: Operation on invalid team
KERN: debug_server: KillTeam(): Error getting info for team 30030: Operation on invalid team
KERN: debug_server: Killing team 30030 ()
KERN: 30049: DEBUGGER: _numBlocks > 0

[kallisti5]

libroot/posix/malloc/superblock.h:  superblock::isValid(void)
libroot/posix/malloc/superblock.h:      assert(_numBlocks > 0);

[kallisti5]

libroot/posix/pthread/pthread.cpp:189:pthread_join(pthread_t thread, void** _value)
.
.
    if ((atomic_or(&thread->flags, THREAD_DETACHED) & THREAD_DEAD) != 0)
        free(thread);
.

[anevilyak]

This looks like the same exact crash as #8836. In the latter case, it's entirely expected due to the pthread spec indicating that performing a join on a detached thread is undefined behavior.

[kallisti5]

Per Pulkomandy, I tested with this version instead: ​https://github.com/haiku/open_posix_testsuite

Same crash.

[korli]

Ingo has deleted this test in 2010: ​http://cgit.haiku-os.org/haiku/commit/?id=2b7695499773e788ef5b01adbdd0d8c6a4d093eb

[kallisti5]

@anevilyak,

ah, you're right.. this is a dup of #8863.

However, if using a thread in this way is common... won't this effect the stability of ports?