#0 0xaaaaaaaa in ?? ()
#1 0xb7f48409 in g_type_class_meta_marshal (closure=0x819afa0,
return_value=0x0, n_param_values=2, param_values=0xaaaaaaaa,
invocation_hint=0xbff068dc, marshal_data=0x44)
at /build/buildd/glib2.0-2.19.10/gobject/gclosure.c:878
callback = <value optimized out>
#2 0xb7f49cab in IA__g_closure_invoke (closure=0x819b200, return_value=0x0,
n_param_values=2, param_values=0x8191118, invocation_hint=0xbff068dc)
at /build/buildd/glib2.0-2.19.10/gobject/gclosure.c:767
marshal = (GClosureMarshal) 0xb7f483c0 <g_type_class_meta_marshal>
marshal_data = (gpointer) 0x44
__PRETTY_FUNCTION__ = "IA__g_closure_invoke"
So param_values changes between the two frames, when the first apparently
calls the second with that value unchanged.
It could be one of a few things, either a race condition due to threads, a
buffer
overflow, or possibly something like a notify on the closure tampering with it
("closure_invoke_notifiers (closure, PRE_NOTIFY);" is called just before).
Thanks,
James
--
console-kit-daemon crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/336792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
