Re: segv on bad gobject get call

Emmanuele Bassi <ebassi gmail com> writes:

you're passing an integer in place of a
blessed scalar wrapping a GObject C instance.

Yes or rather the class name instead of the object instance (the integer
there is a slight furphy, a string property name does it too).

I see the typemap sends a non-object like a class name string to a
"GObject*" of NULL, and that goes to init_property_value(), which calls
G_OBJECT_GET_CLASS and that macro doesn't check, just fetches from NULL.
Are you sure maybe someone along that path shouldn't notice it's bad?

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]