Date: Fri, 25 Jan 2019 19:30:15 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 235158] lang/lua53 no longer linked against pthread Message-ID: <bug-235158-7788-1kVHTRaKQr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235158-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-235158-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235158 --- Comment #18 from i+fbsd@amlegion.org --- (In reply to andrew from comment #16) https://builds.amlegion.org/freebsd_test/dynthr_ktrace.txt That is the ktrace as per the method specified when we did the lua ktrace. This does not exactly hang the same as the lua test case, but that's becaus= e it doesn't mask all signals like cqueues does when creating a thread (if I remember correctly). I do know that cqueues did have the signals masked and that's why it hung and a kill -9 was required and even a CTRL+C (SIGTERM) didn't kill it. The failure exhibited itself with no changes to the code whatsoever, the SIGALARM takes the place of having to CTRL+C and with no signals masked although the thread is hung, one can still get this to exit. No messages ab= out thrashing ever displayed whatosever, and it should have either from the main thread or child thread. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235158-7788-1kVHTRaKQr>