Date: Tue, 17 Jul 2018 13:34:54 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 229830] [truss] throws an assertion failure after the trussed process got killed Message-ID: <bug-229830-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229830 Bug ID: 229830 Summary: [truss] throws an assertion failure after the trussed process got killed Product: Base System Version: 11.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: bsdpr@phoe.frmug.org I used truss to try to identify what syscall caused the kernel to SIGKILL a= jvm and log "out of swap space" to the console while plenty of space was still available in the swap. (This behavior nor this bug report are java-related,= I previously observed it with different commands, I desired to understand that behavior and had a ready test case at hand.) I was unable to observe the curlpit syscall because truss triggered an assertion failure before printing anything related. The assertion is: Assertion failed: (LIST_NEXT(info->curthread, entries) =3D=3D NULL), functi= on find_exit_thread, file /usr/src/usr.bin/truss/setup.c, line 337. The system was compiled from svn revision 329283. --=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-229830-227>