-
-
Notifications
You must be signed in to change notification settings - Fork 99
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
Arm v7 emulation -> panic: Syscall missing: 18023 #300
Comments
is it arm32 or arm64 binary? can you run with -trace -disbytes and show me the failing syscall instruction? |
Might be similar to #25 (comment) - could be a different ABI, or a thumb syscall. |
This could be ARM EABI which passes syscall number in r7. |
Hello, thank you for your answers and sorry for the late reply (could not install usercorn on my laptop).
Hope that helps... Thank you for your help. All the best. |
Hello,
I tried to message on gitter but it looks like the 'usercorn' room is not active.
Apologies if this is not the appropriate place for usercorn questions/problems/issues, here is one from a a newbie.
I am trying to start the execution of a binary compiled for arm (cortex A8 cpu) but I'm facing an error message "panic: Syscall missing: 18023"
I am totaly dumb regarding emulation, how it works, and best practices... But I tried usercorn as an alternative to qemu for running a full application, which is maybe silly.
If that can help, I used Texas Instrument devkit (ti-processor-sdk-linux-am335x-evm-04.03.00.05) as prefix for linked libraries: 'armv7ahf-neon-linux-gnueabi'
I had to create a symbolic link to the ld-linux.so3 before getting this error on execution.
Any help or remark (or question) would be appreciated.
Thank you.
The text was updated successfully, but these errors were encountered: