-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
On Arm64, static file not found results in SIGABRT and hangs #83
Comments
Hello @vinkaga , Please give more details. It would be helpful if you specify:
If I understand correctly this question is about example-hls-media-stream. Regards, |
Hello @vinkaga , do you have any updates on the issue? |
Sorry, just got back from Yosemite :-) I rebuilt oatpp and the example-hls-media-stream on the the target board (Aarch64 Nvidia Jetson Xavier). I ran all the tests and performed a similar test on example-hls-media-stream that was causing SIGABRT on my code. Everything works fine and no SIGABRT. I'll assume that something in my code or cmake is doing it. My next goal would be to integrate into my code (with minimum changes) and repeat the tests. This issue can be closed for now. |
@vinkaga , thank you for the update! Good it works. |
I rebuilt my app on the target board and it works correctly without SIGABRT. I suspect it was a cross-compilation issue. |
@vinkaga Cool! Thank you for the update! Can you describe a bit your app, what is your use-case of the oatpp - just curious. Thank you! |
@lganzzzo, the app is an admin/debug UI for an embedded system. The hardware and software infrastructure would be similar to that of Nvidia Jetson Xavier dev board. |
@vinkaga thank you for describing your project! I have https://oatpp.io/ website served by oatpp. And it's open source (web-site repo). - I guess you may find something to reuse there, like static files server. Regards, |
It works fine on x86_64 but when I run on aarch64/arm64, file not found (the media example) results in SIGABRT and hangs. Any suggestions?
The text was updated successfully, but these errors were encountered: