summary refs log tree commit diff stats
path: root/results/scraper/box64/691
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-16 14:55:48 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-07-16 14:55:48 +0200
commit63d2e9d409831aa8582787234cae4741847504b7 (patch)
tree595fae753d2eb293437226eaab2eed208463f132 /results/scraper/box64/691
parent2843bb65aeaeb86eb89bf3d9690db61b9dc6306e (diff)
downloadqemu-analysis-63d2e9d409831aa8582787234cae4741847504b7.tar.gz
qemu-analysis-63d2e9d409831aa8582787234cae4741847504b7.zip
add box64 bug reports box64
Diffstat (limited to 'results/scraper/box64/691')
-rw-r--r--results/scraper/box64/69114
1 files changed, 14 insertions, 0 deletions
diff --git a/results/scraper/box64/691 b/results/scraper/box64/691
new file mode 100644
index 000000000..d2b87692f
--- /dev/null
+++ b/results/scraper/box64/691
@@ -0,0 +1,14 @@
+[RPi4] BotVice - missing libssl symbol
+While running BotVice, it would seem libssl is missing the 'SSL_load_error_strings'.

+

+Run under the same circumstances as ScourgeBringer. While I've SSL_load_error_strings in the past it's the first time it's a showstopper.

+

+[botvice.txt](https://github.com/ptitSeb/box64/files/11212040/botvice.txt)

+Edit : Similar issue running Nuclear Throne with box86. This may come from the Goldberg emulator when games require specific Steam functions. If that is the case however I feel like wrapping this function would probably be beneficial. This is the best way to run Linux-native Steam games on ARM-based devices, especially low-end ones where you actively don't want the Steam client running in background.

+

+here is the end of the BOX64_LOG=2 log (I can upload the whole thing if needed) :

+[botvice2.txt](https://github.com/ptitSeb/box64/files/11212185/botvice2.txt)

+

+Edit 2: Just to further confirm, box86 suffers from the same missing wrapped function in libssl. Should I create another issue for box86 or should I consider that any missing function for either one will be wrapped for the other as well when creating an issue ?

+

+After looking at libssl's wrapping, load_error_strings seems to be wrapped, so I'm not sure about why this happens. I'll compile an up-to-date libssl and try again !