myzinsky 0 Posted August 14, 2021 Share Posted August 14, 2021 When I start Emby on QNAP I get the following error: ================================================================= Native Crash Reporting ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= ================================================================= Native stacktrace: ================================================================= (No frames) ================================================================= External Debugger Dump: ================================================================= mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb ================================================================= Basic Fault Address Reporting ================================================================= Memory around native instruction pointer (0x76706676):0x76706666 Segmentation fault I have a QNAP TS-420 and I installed the accruing package form: https://emby.media/qnap-server.html Link to comment Share on other sites More sharing options...
Luke 37131 Posted August 14, 2021 Share Posted August 14, 2021 Hi there, what package did you try to install? Link to comment Share on other sites More sharing options...
myzinsky 0 Posted August 14, 2021 Author Share Posted August 14, 2021 First this: https://github.com/MediaBrowser/Emby.Releases/releases/download/4.6.4.0/emby-server-qnap-mono_4.6.4.0_arm-x19.qpkg Second this: https://github.com/MediaBrowser/Emby.Releases/releases/download/4.7.0.7/emby-server-qnap-mono_4.7.0.7_arm-x19.qpkg and then many earlier packages, which then either required mono and libc... which I was not able to manage. Link to comment Share on other sites More sharing options...
PenkethBoy 2063 Posted August 14, 2021 Share Posted August 14, 2021 did you install mono first? and get the correct version of mono supported for your cpu?????? Link to comment Share on other sites More sharing options...
myzinsky 0 Posted August 14, 2021 Author Share Posted August 14, 2021 as far as I understood, mono is not required, since it is part of this package now. Link to comment Share on other sites More sharing options...
PenkethBoy 2063 Posted August 14, 2021 Share Posted August 14, 2021 nope - mono will be required - those packages are compatible and require mono to work Link to comment Share on other sites More sharing options...
myzinsky 0 Posted August 14, 2021 Author Share Posted August 14, 2021 ah okay, but where to get mono for the x19 architecture? Link to comment Share on other sites More sharing options...
PenkethBoy 2063 Posted August 14, 2021 Share Posted August 14, 2021 yep Link to comment Share on other sites More sharing options...
myzinsky 0 Posted August 14, 2021 Author Share Posted August 14, 2021 I installed now this, but still same error... Link to comment Share on other sites More sharing options...
myzinsky 0 Posted August 14, 2021 Author Share Posted August 14, 2021 I also installed gdb, to get more output: ================================================================= Native Crash Reporting ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= ================================================================= Native stacktrace: ================================================================= (No frames) ================================================================= External Debugger Dump: ================================================================= [New LWP 1168] [New LWP 1169] [New LWP 1180] [New LWP 1403] [New LWP 1556] [New LWP 1557] [New LWP 1558] warning: File "/share/MD0_DATA/.qpkg/EmbyServer/lib/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". To enable execution of this file add add-auto-load-safe-path /share/MD0_DATA/.qpkg/EmbyServer/lib/libthread_db-1.0.so line to your configuration file "/root/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/root/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: File "/share/MD0_DATA/.qpkg/EmbyServer/lib/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. 0xb6dc76f0 in waitpid () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 Id Target Id Frame * 1 LWP 1122 "Emby Main Threa" 0xb6dc76f0 in waitpid () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 2 LWP 1168 "SGen worker" 0xb6dc2d18 in pthread_cond_wait () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 3 LWP 1169 "Finalizer" 0xb6dc51ec in ?? () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 4 LWP 1180 "Emby Main Threa" 0xb6dc2d18 in pthread_cond_wait () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 5 LWP 1403 "Thread Pool I/O" 0xb6d0e4e4 in poll () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libc.so.6 6 LWP 1556 "Thread Pool I/O" 0xb6dc3100 in pthread_cond_timedwait () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 7 LWP 1557 "Thread Pool Wor" 0xb6dc5440 in ?? () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 8 LWP 1558 "Thread Pool Wor" 0xb6dc5440 in ?? () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 Thread 8 (LWP 1558 "Thread Pool Wor"): #0 0xb6dc5440 in ?? () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 #1 0xb6dc5574 in sem_timedwait () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 #2 0x0022f8fc in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 7 (LWP 1557 "Thread Pool Wor"): #0 0xb6dc5440 in ?? () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 #1 0xb6dc5574 in sem_timedwait () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 #2 0x0022f8fc in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 6 (LWP 1556 "Thread Pool I/O"): #0 0xb6dc3100 in pthread_cond_timedwait () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 #1 0x0027c090 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 5 (LWP 1403 "Thread Pool I/O"): #0 0xb6d0e4e4 in poll () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libc.so.6 #1 0x001eee30 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 4 (LWP 1180 "Emby Main Threa"): #0 0xb6dc2d18 in pthread_cond_wait () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 #1 0x00000000 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 3 (LWP 1169 "Finalizer"): #0 0xb6dc51ec in ?? () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 #1 0xb6dc52bc in sem_wait () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 #2 0x002218f4 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 2 (LWP 1168 "SGen worker"): #0 0xb6dc2d18 in pthread_cond_wait () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 #1 0x00000000 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (LWP 1122 "Emby Main Threa"): #0 0xb6dc76f0 in waitpid () from /share/MD0_DATA/.qpkg/EmbyServer/lib/libpthread.so.0 #1 0x000880bc in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) [Inferior 1 (process 1122) detached] ================================================================= Basic Fault Address Reporting ================================================================= Memory around native instruction pointer (0x76706676):0x76706666 Link to comment Share on other sites More sharing options...
myzinsky 0 Posted August 14, 2021 Author Share Posted August 14, 2021 58 minutes ago, PenkethBoy said: yep ?? Link to comment Share on other sites More sharing options...
alucryd 216 Posted August 16, 2021 Share Posted August 16, 2021 @PenkethBoy We started providing our own mono builds some time ago because mono is mostly outdated and/or broken on most platforms, and especially on old armv5 devices. We had some luck on the synology side with the same CPU (I think it is), but it looks like qnap will prove more difficult. @myzinsky Could you post the output of the following commands to be sure what CPU and glibc version you have? uname -a cat /proc/cpuinfo ls -la /usr/lib/ld-* Link to comment Share on other sites More sharing options...
alucryd 216 Posted August 16, 2021 Share Posted August 16, 2021 @myzinskyWould be cool if you could provide a binary from your device to see how it was compiled, like the mono binary you got from the qnap repo for instance. Link to comment Share on other sites More sharing options...
Luke 37131 Posted August 24, 2021 Share Posted August 24, 2021 @myzinsky are you able to help with this? Link to comment Share on other sites More sharing options...
myzinsky 0 Posted August 29, 2021 Author Share Posted August 29, 2021 yes Link to comment Share on other sites More sharing options...
Luke 37131 Posted August 30, 2021 Share Posted August 30, 2021 22 hours ago, myzinsky said: yes Can you please provide the information requested above? Thanks ! Link to comment Share on other sites More sharing options...
myzinsky 0 Posted September 5, 2021 Author Share Posted September 5, 2021 Quote uname -a Linux fondue 3.4.6 #1 Thu Jun 24 15:02:12 CST 2021 armv5tel unknown Quote cat /proc/cpuinfo Processor name : Feroceon 88F6282 rev 1 (v5l) @ 1.6 GHz BogoMIPS : 1587.60 Features : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part : 0x131 CPU revision : 1 Hardware : Feroceon-KW ARM Revision : 0000 Serial : 0000000000000000 Quote ls -la /usr/lib/ld-* ls: /usr/lib/ld-*: No such file or directory Link to comment Share on other sites More sharing options...
myzinsky 0 Posted September 5, 2021 Author Share Posted September 5, 2021 Here is the ls binary.... ls Link to comment Share on other sites More sharing options...
Luke 37131 Posted September 5, 2021 Share Posted September 5, 2021 15 minutes ago, myzinsky said: Here is the ls binary.... ls 445.41 kB · 0 downloads What exactly is that from? Link to comment Share on other sites More sharing options...
myzinsky 0 Posted September 5, 2021 Author Share Posted September 5, 2021 1 minute ago, Luke said: What exactly is that from? /bin/ls Link to comment Share on other sites More sharing options...
Luke 37131 Posted September 5, 2021 Share Posted September 5, 2021 8 minutes ago, myzinsky said: /bin/ls Thanks. Link to comment Share on other sites More sharing options...
alucryd 216 Posted September 6, 2021 Share Posted September 6, 2021 (edited) @myzinsky Thanks for the info, not sure why you don't have `/usr/lib/ld-*`, could you try `/lib/ld-*` instead ? Thanks for the binary, it's very helpful. I see the CPU name is arm10tdmi, I'm targeting arm9e which should be compatible, but I guess these old CPUs aren't very well supported anymore. May have to target this specific CPU and create a dedicated tolchain and package, I'll see what I can do. Edited September 6, 2021 by alucryd Link to comment Share on other sites More sharing options...
alucryd 216 Posted September 6, 2021 Share Posted September 6, 2021 There you go: https://github.com/MediaBrowser/Emby.Releases/releases/download/4.7.0.9/emby-server-qnap-mono_4.7.0.9_arm-x19.qpkg This one targets arm10tdmi specifically, hopefully that does the trick. Link to comment Share on other sites More sharing options...
myzinsky 0 Posted September 6, 2021 Author Share Posted September 6, 2021 I will try it! Thanks Link to comment Share on other sites More sharing options...
Luke 37131 Posted September 7, 2021 Share Posted September 7, 2021 Let us know how you get on. Thanks. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now