-
-
Notifications
You must be signed in to change notification settings - Fork 581
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
SEGV when parsing incorrect data in config file #1431
Comments
You are right of course! 😊 |
Thanks again for the bug report. The fix will appear shortly in a Some of them are meant to cause Shairport Sync to exit somewhat gracefully, but they should put a message in the log. |
👍 |
Just FYI, that push to the |
This issue has been inactive for 45 days so will be closed 7 days from now. To prevent this, please remove the "stale" label or post a comment. |
Just had my system crashing here. After some debugging, I figured, that there was an incorrect entry in the configuration file:
With this (incorrect) configuration, shairport-sync (latest development release) crashed with a segmentation fault. I understand that the configruation is incorrect, but sahirport-sync should ignore it, report it or something like this, not crash.
The text was updated successfully, but these errors were encountered: