GNOME Bugzilla – Bug 580296
Segfault during documentation generation
Last modified: 2009-05-11 05:28:53 UTC
Version 0.7.5 15:57 <@JHM> goffice 0.7.5 is not making me happy. 15:59 <@JHM> On i386 (well, i386 chroot on amd64), I get segfaults from goffice-0.8-scan . 15:59 <@JHM> goffice-0.8-scan.c:129 is "object_types[i++] = go_conf_get_type ();" 16:00 <@JHM> This results in go_conf_get_type being called with bogus values, 16:00 <@JHM> thus calling get_schema with node being NULL or something invalid, 16:01 <@JHM> thus segfaulting when node is dereferenced in get_schema. 16:01 <@JHM> The node == NULL case is easy to fix, 16:01 <@JHM> but with an optimised (-O2) build, node is invalid rather than NULL. 16:10 < jean> hmm, the go_conf code is not that new 16:18 < jean> ah, I see, we should probably rename it go_conf_get_key_type or so 16:18 < jean> strange this did not appeared earlier 16:19 < jean> go_conf_get_node_type is better 16:23 <@JHM> Sounds fine to me - this should prevent gtk-doc from trying to scan it. 16:25 < jean> please file a bug report This is what this looks like (with the ...docs/reference/goffice-0.8-scan script instrumented to call gdb): (gdb) where
+ Trace 214815
Created attachment 133332 [details] [review] fixes the build issue It should not break anything since it seems that this function was just used internally.
Fixed.
Used go_conf_node_get_key_type finally.
*** Bug 580377 has been marked as a duplicate of this bug. ***