GNOME Bugzilla – Bug 736780
[PATCH] load_device_factories SEGFAULT due to bad cast
Last modified: 2014-09-17 09:32:53 UTC
Created attachment 286341 [details] [review] [PATCH] core: Fix casting of factory type See attached patch. Traceback: Program received signal SIGSEGV, Segmentation fault. 0x00007fb049544c42 in g_type_fundamental (type_id=type_id@entry=1320500320) at gtype.c:3960 3960 return node ? NODE_FUNDAMENTAL_TYPE (node) : 0; Missing separate debuginfos, use: debuginfo-install dbus-glib-0.100.2-2.fc20.x86_64 glibc-2.18-14.fc20.x86_64 gvfs-1.18.3-3.fc20.x86_64 libbluray-0.6.1-1.fc20.x86_64 libndp-1.4-1.fc20.x86_64 libnl3-3.2.24-3.fc20.x86_64 libsoup-2.44.2-1.fc20.x86_64 libuuid-2.24.2-1.fc20.x86_64 libxml2-2.9.1-2.fc20.x86_64 nspr-4.10.7-1.fc20.x86_64 nss-3.17.0-1.fc20.x86_64 nss-softokn-3.17.0-1.fc20.x86_64 nss-softokn-freebl-3.17.0-1.fc20.x86_64 nss-util-3.17.0-1.fc20.x86_64 polkit-0.112-2.fc20.x86_64 readline-6.2-10.fc20.x86_64 sqlite-3.8.6-2.fc20.x86_64 (gdb) bt
+ Trace 234100
The patch is OK. Just nitpicking, any reason to use g_slist_next instead of direct next access? NM code style puts a space before opening parenthesis.
Created attachment 286347 [details] [PATCH v2] core: Fix casting of factory type (In reply to comment #1) > The patch is OK. > Just nitpicking, any reason to use g_slist_next instead of direct next access? > NM code style puts a space before opening parenthesis. Not good reason really; just a leftover from debugging (I initially thought it's not okay to access the next pointer directly). Attaching a version without that unnecessary change.
Created attachment 286348 [details] [review] [PATCH v3] core: Fix casting of factory type whoops
Review of attachment 286348 [details] [review]: OK
Pushed to master: b05c8db core: fix casting of factory type (bgo #736780)