Open Vaelatern opened 11 months ago
Broken on glibc too. Due to breaking change in wxwidget
Interestingly the dbg repo for x86_64-musl results in a prusa-slicer binary that has an exec format error on launch.
/usr/lib/debug/usr/bin/prusa-slicer: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter *empty*, BuildID[sha1]=75d716275ac4ba701be3c8062a2a09128e906a5d, with debug_info, not stripped
We may need this patch https://github.com/prusa3d/PrusaSlicer/commit/e21921f2ebd2b94c57459bd280f1b1bd8eec1b9c
I'll test
It'll need more than just that...
Interestingly the dbg repo for x86_64-musl results in a prusa-slicer binary that has an exec format error on launch.
I think that's true for all dbg packages; they ship ELFs containing the debuginfo and not the machine code. Also partly evidenced by interpreter *empty*
Some tools like gdb will be able to locate the separate debuginfo file in /usr/debug
. If the tool doesn't support that, you may be able to use eu-unstrip
to recombine the two files
Adding a backtrace from my experience of the segfault in case it helps figuring out what's going on, though I guess the referenced function is in the patch above.
from /usr/lib/libstdc++.so.6
Any difference with the more recent 2.7 branch?
Is this a new report?
Yes
System Info
Void 6.3.13_1 x86_64-musl GenuineIntel notuptodate rrnDDFFFFFFFFF
Package(s) Affected
PrusaSlicer-2.5.2_3, wxWidgets-common-3.2.2.1_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
Should be able to start
Actual behaviour
Steps to reproduce