Date: Mon, 23 Jan 2017 08:18:10 +0000 From: bugzilla-noreply@freebsd.org To: mono@FreeBSD.org Subject: [Bug 211367] lang/mono net-p2p/sonarr Sonarr crashes on startup with SIGSEGV since base r296727 on 10.3-STABLE Message-ID: <bug-211367-23699-s7XpiQ0PVJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-211367-23699@https.bugs.freebsd.org/bugzilla/> References: <bug-211367-23699@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=3D211367 Phil <pmichel@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmichel@gmail.com --- Comment #27 from Phil <pmichel@gmail.com> --- I just swapped motherboards / CPUs from a single Xeon E3 to now 2x Xeon E5s. Nothing else needed configuring and everything works fine EXCEPT I now get a nearly identical error to the one reported here when running mono with not = just NzbDrone.exe but any executable: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries=20 used by your application. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D If I load the dumped core, I get: gdb mono-sgen mono-sgen.core=20 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... Core was generated by `mono-sgen'. Program terminated with signal 6, Aborted. Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /usr/local/lib/libinotify.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libinotify.so.0 Reading symbols from /lib/libthr.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x00000008012aa50a in thr_kill () from /lib/libc.so.7 [New Thread 801816000 (LWP 100910/<unknown>)] (gdb) where #0 0x00000008012aa50a in thr_kill () from /lib/libc.so.7 #1 0x00000008012aa4db in raise () from /lib/libc.so.7 #2 0x00000008012aa449 in abort () from /lib/libc.so.7 #3 0x00000000004a56e2 in mono_debugger_run_finally () #4 0x0000000000417e00 in mono_get_jit_info_from_method () #5 0x0000000800fca79d in pthread_sigmask () from /lib/libthr.so.3 #6 0x0000000800fc9d6f in pthread_getspecific () from /lib/libthr.so.3 #7 <signal handler called> #8 0x00000000006366b5 in mono_gchandle_free () #9 0x00000000005bd734 in mono_init () #10 0x0000000000418bec in mini_get_debug_options () #11 0x0000000000473ffc in mono_main () #12 0x00000000004156fa in _start () #13 0x000000000041516f in _start () #14 0x000000080098b000 in ?? () #15 0x0000000000000000 in ?? () So it looks very similar to the bug reported above.=20 I'm running 11.0-RELEASE-p2 (GENERIC) and mono 4.6.2 (latest pkg) in a jail. I've tried running it on the host system, with the same error. I've also tried building from source (poudriere) and the build fails due to= a similar SIGSEGV: if test -w /wrkdirs/usr/ports/lang/mono/work/mono-4.6.2/mcs; then :; else c= hmod -R +w /wrkdirs/usr/ports/lang/mono/work/mono-4.6.2/mcs; fi cd /wrkdirs/usr/ports/lang/mono/work/mono-4.6.2/mcs && gmake --no-print-directory -s NO_DIR_CHECK=3D1 PROFILES=3D'binary_reference_assem= blies net_4_x xbuild_12 xbuild_14 ' CC=3D'cc' all-profiles mkdir -p -- build/deps gmake[7]: mcs: Command not found gmake[7]: *** [build/profiles/basic.make:93: build/deps/basic-profile-check.exe] Error 127 *** The compiler 'mcs' doesn't appear to be usable. *** Trying the 'monolite' directory. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries=20 used by your application. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D gmake[9]: *** [build/profiles/basic.make:93: build/deps/basic-profile-check.exe] Abort trap (core dumped) Any reason this bug would re-appear on a multi-processor system? --=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-211367-23699-s7XpiQ0PVJ>