Closed Mabbs closed 3 months ago
Can you grab the core dump and copy and paste the backtrace (type bt
after you load the core dump)?
https://docs.darlinghq.org/contributing/debugging.html#debug-with-core-dump
Can you grab the core dump and copy and paste the backtrace (type
bt
after you load the core dump)?https://docs.darlinghq.org/contributing/debugging.html#debug-with-core-dump
Sure, this is my core dump file: core_dump.34453.zip
and this is backtrace:
(lldb) bt
* thread #1, name = 'darlingserver', stop reason = signal SIGILL
* frame #0: 0x00007f8c2233f307 libc.so.6`epoll_wait + 87
frame #1: 0x000000000040e061 darlingserver`DarlingServer::Server::start() + 913
frame #2: 0x000000000040bcdc darlingserver`main + 3164
frame #3: 0x00007f8c2223a7e5 libc.so.6`__libc_start_main + 229
frame #4: 0x000000000040a69e darlingserver`_start + 46
Hmm... this might be an issue with mldr
and not darlingserver
. Can you copy and paste the output of coredumpctl list -r
?
Hmm... this might be an issue with
mldr
and notdarlingserver
. Can you copy and paste the output ofcoredumpctl list -r
?
TIME PID UID GID SIG COREFILE EXE
Fri 2024-03-22 23:03:19 CST 32543 0 0 4 present /usr/local/bin/darlingserver
Fri 2024-03-22 23:03:19 CST 32542 0 0 4 none /usr/local/bin/darling
Fri 2024-03-22 22:45:58 CST 32212 0 0 4 present /usr/local/bin/darlingserver
Fri 2024-03-22 22:45:58 CST 32211 0 0 4 none /usr/local/bin/darling
Fri 2024-03-22 22:42:18 CST 32148 0 0 4 present /usr/local/bin/darlingserver
Fri 2024-03-22 22:42:18 CST 32147 0 0 4 none /usr/local/bin/darling
Looks like darling
is crashing... Can you copy and paste the backtrace for it?
Oh wait... It says a core file is not present...
I changed my computer and still have the same error:
root@mayx-server:/home/mayx# neofetch
.-/+oossssoo+/-. root@mayx-server
`:+ssssssssssssssssss+:` ----------------
-+ssssssssssssssssssyyssss+- OS: Ubuntu 22.04.4 LTS x86_64
.ossssssssssssssssssdMMMNysssso. Kernel: 5.15.0-101-generic
/ssssssssssshdmmNNmmyNMMMMhssssss/ Uptime: 13 mins
+ssssssssshmydMMMMMMMNddddyssssssss+ Packages: 899 (dpkg), 4 (snap)
/sssssssshNMMMyhhyyyyhmNMMMNhssssssss/ Shell: bash 5.1.16
.ssssssssdMMMNhsssssssssshNMMMdssssssss. CPU: AMD Athlon II X4 641 (4) @ 2.800GHz
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ GPU: NVIDIA GeForce GT 440
ossyNMMMNyMMhsssssssssssssshmmmhssssssso Memory: 264MiB / 3891MiB
ossyNMMMNyMMhsssssssssssssshmmmhssssssso
+sssshhhyNMMNyssssssssssssyNMMMysssssss+
.ssssssssdMMMNhsssssssssshNMMMdssssssss.
/sssssssshNMMMyhhyyyyhdNMMMNhssssssss/
+sssssssssdmydMMMMMMMMddddyssssssss+
/ssssssssssshdmNNNNmyNMMMMhssssss/
.ossssssssssssssssssdMMMNysssso.
-+sssssssssssssssssyyyssss+-
`:+ssssssssssssssssss+:`
.-/+oossssoo+/-.
root@mayx-server:/home/mayx# darling shell
Bootstrapping the container with launchd...
Illegal instruction (core dumped)
The problem has been found. Because my CPU does not support SSE3, I used https://github.com/mirh/opemu-linux to make it work properly
Expected Result Open a shell.
Actual Result (base) [root@localhost ~]# darling shell Bootstrapping the container with launchd... Illegal instruction (core dumped)
Steps To Reproduce after build, I use this command
darling shell
strace
Output Is too long: output.txtdmesg
Output Rundmesg | grep 'overlay\|darling'
System Information