GNOME Bugzilla – Bug 545575
gdmsetup crashed with SIGSEGV in g_main_context_dispatch()
Last modified: 2012-07-06 01:49:54 UTC
the bug has been opened on https://launchpad.net/bugs/252973 "This was originally reported in https://bugs.launchpad.net/bugs/246088, but was closed requesting that a new crash file be submitted via apport.
+ Trace 204211
It does not happen with e.g. synaptic, but happens every time with gdmsetup. I am running from a root shell after running "sudo su". http://launchpadlibrarian.net/16428082/valgrind.log * valgrind.log (277.8 KiB, text/plain) ==9923== ==9923== Jump to the invalid address stated on the next line ==9923== at 0x0: ??? ==9923== by 0x5268DD8: run_in_thread (gsimpleasyncresult.c:613) ==9923== by 0x52628C1: run_job_at_idle (gioscheduler.c:197) ==9923== by 0x46E41E0: g_idle_dispatch (gmain.c:4090) ==9923== by 0x46E5DD5: g_main_context_dispatch (gmain.c:2012) ==9923== by 0x46E9192: g_main_context_iterate (gmain.c:2645) ==9923== by 0x46E9576: g_main_loop_run (gmain.c:2853) ==9923== by 0x4195263: gtk_main (in /usr/lib/libgtk-x11-2.0.so.0.1200.9) ==9923== by 0x80655F1: main (in /usr/sbin/gdmsetup) ==9923== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==9923== ==9923== Process terminating with default action of signal 11 (SIGSEGV) ==9923== Bad permissions for mapped region at address 0x0 ==9923== at 0x0: ??? ==9923== by 0x5268DD8: run_in_thread (gsimpleasyncresult.c:613) ==9923== by 0x52628C1: run_job_at_idle (gioscheduler.c:197) ==9923== by 0x46E41E0: g_idle_dispatch (gmain.c:4090) ==9923== by 0x46E5DD5: g_main_context_dispatch (gmain.c:2012) ==9923== by 0x46E9192: g_main_context_iterate (gmain.c:2645) ==9923== by 0x46E9576: g_main_loop_run (gmain.c:2853) ==9923== by 0x4195263: gtk_main (in /usr/lib/libgtk-x11-2.0.so.0.1200.9) ==9923== by 0x80655F1: main (in /usr/sbin/gdmsetup)"
updated debug stacktrace: "#0 0x00000000 in ?? ()
+ Trace 204212
Looks like something is passing NULL as function to g_simple_async_result_run_in_thread ? Hard to tell where that happens, from this stacktrace.
do you have any idea on how to get extra details about the issue?
Dunno. Maybe break in g_simple_async_result_run_in_thread witch condition func == NULL.
g_simple_async_result_run_in_thread has "g_return_if_fail (func != NULL)" So, this should report some spew somewhere. You could break in g_log to find it.
Assuming that more details are not going to come at this point. Closing