On Saturday, August 19, 2023 11:53:35 A.M. CDT you wrote: > Hi Steve, > > I'm afraid, it doesn't prevent digikam from crashing. > > Here is what I did (after fetching the latest updates from "testing" this > morning):
[ ... ] > Not sure if my approach is the preferred way to test something across > different branches, though. I didn't want to switch my entire system to > "sid" (this is my main machine, after all :) ). Hope that's OK. If there's > a better way of testing your version, please let me know. The testing approach is fine. Thanks for this. Given the gdb stack trace, this result is what I expected. I don't understand what the illegal instruction is at that address. I have two ideas at this point. 1. Test a build without SSE4. If you feel up to it, this would be easiest to do on your machine because the build-time detection should simply work fine. If you have sufficient time and interest, please look at https:// www.linuxfordevices.com/tutorials/debian/build-packages-from-source If you aren't able to build from sources, let me know. The alternative is for me to build it here after hacking the sources to disable SSE4 detection. 2. Dig further with the debugger to understand what the illegal instruction is. I may be completely wrong in assuming it is an SSE4 instruction -- particularly given the fact that the test code we discussed August 13/14 builds the same with/without the -msse4.1 flag. If you are handy with gdb you can probably dig into the assembly and figure out what the instruction is. Regards, -Steve
signature.asc
Description: This is a digitally signed message part.
