I recently installed mono 2.6.7 on my debian lenny and I am trying to run a minecraft server. Everything I run the mono command i get the error from below:
Stacktrace
Native stacktrace
mono [0x536e71]
mono [0x43f5ed]
/lib/libpthread.so.0 [0x2ba796fa4a80]
mono [0x43f571]
/lib/libpthread.so.0 [0x2ba796fa4a80]
[0x40136834]
=================================================================
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.
=================================================================
Aborted (core dumped)
Any idea on what would fix this?
Related
[SOLVED] Qt version in qtchooser was 4. All work after version changing.
I recently tried to use Qt in Rust. When I add qt_widgets to my dependencies, I get an error:
error: failed to run custom build command for `qt_widgets v0.5.0`
Caused by:
process didn't exit successfully: `/home/alex/first/target/debug/build/qt_widgets-6acdb9fff7eba7cd/build-script-build` (exit code: 1)
--- stderr
[2020-06-23T19:17:50Z ERROR ritual_common::errors] Error:
[2020-06-23T19:17:50Z ERROR ritual_common::errors] only Qt 5 is supported! "4.8.7" is not supported
Qt 5.15.0 and Qt 4.8.7 are installed in my system.
I'm using .NET CORE 2.1.1 on a ARM32 Linux Iot board (Raspberry Pi3B+).
I've collected a crash dump for my console app, by following the analyzing dump on linux, I'm trying to do a analysis via lldb.
the post seems a bit old, the path of libsosplugin.so now changed under to /opt/dotnet/shared/Microsoft.NETCore.App/2.1.1/, meanwhile, I can't see anything from command ldd libsosplugin.so | grep lldb, and this is my ldd libsosplugin.so result:
linux-vdso.so.1 (0x7edcb000)
/usr/lib/arm-linux-gnueabihf/libarmmem.so (0x76ee4000)
libstdc++.so.6 => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0x76d87000)
libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0x76d08000)
libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0x76cdb000)
libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0x76b9c000)
/lib/ld-linux-armhf.so.3 (0x76f10000)
so I have no way to know what it the target lldb, then I have to try from lldb-3.5 to lldb-4.0 via apt-get install lldb-x.x one by one.
I've noticed, 3.5 - 3.9 have the issue to accept my key stroke! all key strokes were interpreted as a Uncode string, finally, lldb-4.0 can load the dump and plugin:
plugin load /opt/dotnet/shared/Microsoft.NETCore.App/2.1.1/libsosplugin.so
setclrpath /opt/dotnet/shared/Microsoft.NETCore.App/2.1.1
but once I key in sos PrintException, lldb crashed it self with Segmentation fault, everything listed below:
pi#raspberrypi:~/crash_dumps $ lldb-4.0 $(which dotnet) --core ./core.dotnet.1402.raspberrypi.1533274692
(lldb) target create "/usr/local/bin/dotnet" --core "./core.dotnet.1402.raspberrypi.1533274692"
Core file '/home/pi/crash_dumps/./core.dotnet.1402.raspberrypi.1533274692' (arm) was loaded.
(lldb) plugin load /opt/dotnet/shared/Microsoft.NETCore.App/2.1.1/libsosplugin.so
(lldb) setclrpath /opt/dotnet/shared/Microsoft.NETCore.App/2.1.1
(lldb) sos PrintException
(lldb)
Stack dump:
0. HandleCommand(command = "")
Segmentation fault (core dumped)
As far as I know libsosplugin.so shipped with .NET Core SDKs 2.1.30x (.NET Core 2.1) requires lldb-3.8 or lldb-3.9, so I'd expect 4.0 version to throw all sorts of errors including segfault.
Not sure why you're having unicode issue, though. When I used lldb-3.9 for .NET Core it did print character codes for certain keys (up, Ctrl+), but the rest was fine and that was x64, not ARM. Maybe that's the separate issue caused by environment settings that can be googled separately.
I'm novice in cross-compiling and just started to cross-compile packages on my linux machine (amd64) for host (NAS) with ARMv5 (linux kernel 2.6.31.8). I installed crosstool-ng and with it created toolchain for compilation for ARM. According to some tutorials online I succeeded to compile x264 package. But now when I try to run it, I was given the following error message
./x264: /lib/libm.so.6: version 'GLIBC_2.15' not found (required by ./x264)
Ok now I see that I need libm library but what it is and how to compile x264 with it?
From the error message: the version of x264 you built requires version of glibc 2.15. The Glibc is built as part of your cross compilation toolchain (through crosstool-ng).
You need to build a new toolchain with the same version of glibc found on your NAS root filesystem (or compatible).
(edited after #NotLikeThat comment)
I'm trying to get the latest mono (version 3.12.0) to compile on my raspberry pi 2 running raspbian linux (based on debian).
I've downloaded the mono source and compiling seems to be going well then I hit an error when compiling 'mcs/class/aot-compiler'
the error is that it cannot find './../../class/lib/net_4_5/mscorlib.dll.so'
I've checked the directory and I see that mscorlib.dll was compiled along with an .mdb file but I do not see an so file.
Do I need to specify a switch or something to build the so file? (I'm a linux newb)
Where is the make file that's building mscorlib? compiling is taking forever for the whole source, can I just recompile mscorlib and have an so file emitted somehow?
When I try to run my VB.NET application on Debian 6 x86 I get this error:
WARNING **: The class System.Collections.Generic.List`1 could not be loaded, used in mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Stacktrace:
Native stacktrace:
mono() [0x80d5b19]
mono() [0x810f7ab]
[0xb774f600]
mono() [0x80620b8]
mono() [0x80637bf]
mono() [0x80645c8]
mono(mono_runtime_invoke+0x40) [0x81cbab0]
mono(mono_runtime_exec_main+0xde) [0x81cf55e]
mono(mono_runtime_run_main+0x112) [0x81cf862]
mono(mono_main+0x15ec) [0x80b3bdc]
mono() [0x805b675]
/lib/libc.so.6(__libc_start_main+0xe6) [0xb74fdc96]
mono() [0x805b5b1]
Debug info from gdb:
=================================================================
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.
=================================================================
Aborted
How can I fix this? It doesn't look like my application is causing it, I was able to run the application on another machine with another distro.
The issue was caused because apt-get was installing older versions of mono. However, Ubuntu 12.10 seems to install a newer version.