libcrypto performs cpu feature checks on ARM platforms, by calling `OPENSSL_cpuid_setup`.
In there, it tries to call various instructions and traps `illegal instructions` aka. non-existing instructions itself.
However, as hyperion.ng also tries to trap all signals, the call inside libcrypto is propagated and hyperiond gets killed by itself.
This patch lets execution proceed, even when `SIGILL` occurs.
References:
- libcrypto OPENSSL_cpuid_setup: 954f45ba4c/crypto/armcap.c (L183)
* Stop Web-Capture when priority changes
* Remote control UI: Treat duration=0 as endless
* Stop Web-Capture on non-Image events changes
* LED Matrix Layout - Support vertical cabling direction
* Additional Yeelight models
* Treat http headers case insensitive
* Update change log
* Treat http headers case insensitive (consider Qt version)
* API - Consider provided format when setImage
* UI - Support Boblight configuration per LED instance
* Support multiple Boblight clients with different priorities
* Update changelog
* Simplify isGUI rules allowing for QT only builds
* Sysinfo: Fix indents
* LED-Devices: Show warning, if get properties failed
* Qt-Grabber: Fixed position handling of multiple monitors
* LED layout: Remove indention limitations
* Yeelight: Test YLTD003
* hyperion-remote: Provide image filename to muxer/UI
* Refactor PriorityMuxer and related
* Temp: Build under Windows 2019
* Yeelight: Remove YLTD003 as it is not working without additional changes
* Test Windows-latest with out removing redistributables/new MSVC
* correct workflows
* correct CI script
* Build Windows with Qt 5.15.2
* Priority Muxer: Updates after testing
* Fix Typo
* Update BGHandler
* QTGrabber - Reactivate windows code to avoid cursor issues
* Emit prioritiesChanged when autoselect was changed by user
Co-authored-by: Paulchen Panther <Paulchen-Panter@protonmail.com>
* Fix too much copy/paste
* Fix typo
* Commandlineoptions: Additional error details for Int and Double ranges
* Standalone grabbers: Show fps range on error, fix default host address
* add britisch flags to flag.py
adding the flags of England, Scotland and the United Kingdom to flag.py
* adding British flags to flag.schema.json
adding the flag of Great Britain (gb), England (gb-eng) and Scotland (gb-sct) to the GUI
* added flag updates to CHANGELOG.md
mentioning the Britisch flags as well as Cameroon and Russia
* LedDevice - Address clang findings
* Fix Windows Warnings
* Ensure newInput is initialised
* Clean-up unused elements for Plaform Capture
* Fix initialization problem and spellings
* Address clang findings and spelling corrections
* LedDevice clean-ups
* Cleanups
* Align that getLedCount is int
* Have "display" as default for Grabbers
* Fix config during start-up for missing elements
* Framegrabber Clean-up - Remove non supported grabbers from selection, filter valid options
* Typo
* Framegrabber.json - Fix property numbering
* Preselect active Grabbertype
* Sort Grabbernames
* Align options with selected element
* Fix deletion of pointer to incomplete type 'BonjourBrowserWrapper'
* Address macOS compile warnings
* Have default layout = 1 LED only to avoid errors as in #673
* Address lgtm findings
* Address finding that params passed to LedDevice discovery were not considered
* Cleanups after merging with latest master
* Update Changelog
* Address lgtm findings
* Fix comment
* Test Fix
* Fix Python Warning
* Handle Dummy Device assignment correctly
* Address delete called on non-final 'commandline::Option' that has virtual functions but non-virtual destructor
* Correct that QTimer.start accepts only int
* Have Release Python GIL & reset threat state chnage downward compatible
* Correct format specifier
* LedDevice - add assertions
* Readonly DB - Fix merge issue
* Smoothing - Fix wrong defaults
* LedDevice - correct assertion
* Show smoothing config set# in debug and related values.
* Suppress error on windows, if default file is "/dev/null"
* CMAKE - Allow to define QT_BASE_DIR dynamically via environment-variable
* Ignore Visual Studio specific files
Co-authored-by: Paulchen Panther <16664240+Paulchen-Panther@users.noreply.github.com>
* Allow --version, even if hyperion is already running
* Add CPU-Model to SysInfo
* Add additional CPUInfos
* Use fileUtils & RegEx on CPU-Info
* Add CPU - Hardware info
* Update changelog
* Suppress empty CPU info elements
