-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AxRuntime (41.1) crashes on starting Wanderer on Debian Buster #63
Comments
Suspected of misaligned stack together with SSE instructions. Output of lscpu
|
Can you download this package: https://www.axrt.org/download/aros/v11/AROS-20211231-1-linux-x86_64-system.tar.bz2 and tell me if it crashes the same way when starting AROS? Additional question: can you do "gcc --version" and paste here? |
Package downloaded and started. Seem to crash at the same location with same error. The bootstrap outputs:
The bootstrap keeps repeating this over and over again. Therefore i do not have a gdb stacktrace that is helpful (as it traces back to the point where i pressed ctrl-c in order to stop the (error)loop. gcc version reads:
fwiw: in the compile log (from compiling axrt) i am able to locate a lot of messages reading:
|
Accidently closed the issue |
Ok, so the problem is related to AROS core on your CPU, not to your system/compiler. I will investigate further. |
here is disassembly from running wanderer with axrt
In the hope it is useful. |
Thank you. Can you do one more thing: one you get the crash, please do
This should show the value of RBP register. |
just as a sidemark, if you did not notice the illegal command "vmovdqa" here is an AVX command, which is correct identified as illegal, because his CPU has no AVX extension, the question is why it creates AVX commands even his CPU does not support them? |
Thanks - I did not notice that. That will make it easier to trace the problem. |
Please do the following: This should rebuild utility.library with setmem_sse compiled without AVX opcodes. You can check alt-runtimelinux-x86_64-d/bin/runtimelinux-x86_64/gen/rom/utility/utility/arch/setmem_sse.o if they are gone. If this solves your issue, I will push the change to repository. |
Sorry in advance for my need for extra guidance.
I needed to start from scratch, so therefor I did things a bit differently. In case this answer is not helpful in what you wanted/needed to know from me then please correct. I did the following:
Before building there wasn't a directory available named: alt-runtimelinux-x86_64-d/bin/runtimelinux-x86_64/gen/rom/utility/utility/arch so I am not sure where that comes into place as suggested by your instructions. I am assuming it needed to be cleaned out before running make. If so then it was clean beforehand.
After the rebuild script finished, the following files were present inside the directory as mentioned:
Please advice. TIA |
Easiest is just to start Wanderer and see if you again get a crash in SetMem_SSE :) |
@Deadw00D: Wanderer is showing its face now without crashing. Not much to do/test without a working left mouse-button but, it's still progress. Thank you. Issue can be closed, unless you prefer it to be closed after you pushed your changes (and have me checked it out first) ? |
Thanks, I need to make these changes clean, push them and then I will close the bug. |
Use -mavx only for setmem_avx. Otherwise gcc generates AVX versions of vmovdqa opcode to handle XMM registers.
Starting Wanderer on a debian (stable 10 buster) derivative results in the following output:
gdb debug log:
gdb backtrace:
Suggested workaround as mentioned on aros-exec forum (*) circumvents the crash.
(*) One workaround might be to go to AROS/arch/x86_64-all, delete utility directory there and rebuild.
The text was updated successfully, but these errors were encountered: