What appears to have happened here is that 0x6000000 was treated as a
closure, which it wasn't, and the field read from there as the pointer
to the code must have been 0x0. The trouble is that we have no way of
knowing from this what the closure was *supposed* to be, unless we can
reproduce the bug.
Can you, in fact, reproduce this bug?
** Changed in: compiz (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746848
Title:
compiz crashed with SIGSEGV in g_closure_invoke()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/746848/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
