I do not know how to recreate this bug, but it is fairly clear that the
g_hash_table_lookup_node function called by g_hash_table_remove_internal
has some serious issues with null pointers.
My debugger is pointing me to the line of code which says:
while ((node = *node_ptr))
and when I ask it for the value of node_ptr it says it is 0x0. So
clearly *node_ptr will have problems with that if true.
However, I cannot figure out how this is possible, hence I'm not sure
how to recreate the bug. If someone can find steps for that to occur,
then it would be very useful.
--
console-kit-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/196724
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
