GNOME Bugzilla – Bug 720372
Rygel segfaults when the port is set to a non-0 value in rygel.conf
Last modified: 2013-12-14 14:56:43 UTC
I'm seeing the following crash when setting the port to a non-0 value (e.g. "4004" in my case).
Here's the backtrace:
This is with gupnp-0.20.8. It doesn't occur with gupnp-0.20.5. Not sure about the intermediate versions.
--prefix=blah --enable-uninstalled --disable-tracker-plugin --enable-gst-launch-plugin --enable-vala --enable-debug
cp data/rygel.conf ./
change "port=0" to "port=4004"
src/rygel/rygel -c ./rygel.conf
Let me know if there's any other information I can provide.
OK - another important data point:
Everything I had was current except my gssdp which was behind (version 0.14.3, commit e4c8a58). And updating gssdp to version 0.14.6 (commit 357f083) prevents this segfault.
Strange as it isn't in the backtrace. But I see there were changes to ssdp related to setting the port at startup. So it seems there must be a relationship here.
Created attachment 264131 [details] [review]
context: Ensure msearch-port property exists before setting
Fix a typo that crashes gupnp_context_constructor() if msearch-port
property does not exist (it was added in gssdp 0.14.6).
Yeah - that definitely lines up with the backtrace.
I'll apply the change and confirm.
Confirmed the patch resolves the segfault
(Reverted gssdp to 0.14.3, confirmed segfault, applied patch, built, and re-tested)
I'm sure I have the status all wrong on this bug. Please update appropriately. Thx!
Review of attachment 264131 [details] [review]:
Attachment 264131 [details] pushed as 485d15d - context: Ensure msearch-port property exists before setting