[Bug 221132] [NEW PORT] security/sandsifter: x86 processor fuzzer

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Aug 1 18:48:18 UTC 2017


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221132

--- Comment #11 from rozhuk.im at gmail.com ---
Created attachment 184923
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184923&action=edit
coredump

I got coredump for process only at the end of scanning:

#0  0x0000000800968931 in pthread_sigmask () from /lib/libthr.so.3
(gdb) bt
#0  0x0000000800968931 in pthread_sigmask () from /lib/libthr.so.3
#1  0x0000000800967908 in pthread_getspecific () from /lib/libthr.so.3
#2  0x00000008009677c4 in pthread_getspecific () from /lib/libthr.so.3
#3  0x0000000800970029 in pthread_attr_getaffinity_np () from /lib/libthr.so.3
#4  0x000000080096a308 in pthread_mutex_destroy () from /lib/libthr.so.3
#5  0x0000000800969906 in pthread_mutex_lock () from /lib/libthr.so.3
#6  0x0000000000401cb5 in sync_fflush ()
#7  0x0000000000403a8e in give_result ()
#8  0x0000000000404492 in main ()

And same errors I got some times in another apps.
Not sure, may be this starts after upgrade to ryzen.

FreeBSD rimwks 11.1-STABLE FreeBSD 11.1-STABLE #0 r321518M: Wed Jul 26 17:09:26
MSK 2017     root at rimwks:/usr/obj/usr/src/sys/RIMWKSx64  amd64

I have no idea why and what syscall missed in your system.
And why my system not crash without kib patch.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list