This is due to musl now being a bit more strict about application bugs. After asking in #musl the reply was "you should report that calling pthread_join on a detached thread is undefined behaviour". Backtrace can be found here: https://github.com/openwrt/packages/issues/7473#issuecomment-453838290
Discussion
-
medoc
2019-01-16Hi,
actually this looks like a pupnp/libupnp bug, it's in libupnp code and upmpdcli/libupnpp does not use detached threads at all as far as I can see.
https://github.com/mrjimenez/pupnp/issuesAlso if the stack is right, pthread_detach itself calls pthread_join so something is weird:
#1 0xb6fd68f8 in __pthread_join (t=<optimized out>, res=res@entry=0x0) at src/thread/pthread_join.c:28 #2 0xb6fd669c in __pthread_detach (t=<optimized out>) at src/thread/pthread_detach.c:11
-
medoc
2019-01-16- status: open --> closed
- milestone: -->
-
Anonymous
2019-01-19I see, thanks for having a look