Bug#840430: glib2.0: segfaults in nemo when opening files from the desktop

[Norbert Preining]

HI Jason,

thanks for your email.

> You could try setting the environment variable G_SLICE=debug-blocks so
> glib will abort if it detects invalid memory releases.  That will

Ok, tried that, started nemo, made it crash, got
	GSlice: MemChecker: attempt to release non-allocated block: 0x2dc8100 size=64

> hopefully tell you where the invalid release happens, instead of
> possibly crashing much later after memory has been corrupted.

Immediately after that it crashed.

> Alternatively, valgrind can help find invalid memory reads and writes.

I tried valgrind - but it is my first time. It gave me *loads* of output,
many many traces starting with
	Invalid read of size 8
	Invalid write of size 8

and two of
	Invalid free() / delete / delete[] / realloc()

Then, at the end, there is:
==1075== Process terminating with default action of signal 11 (SIGSEGV)
==1075==  Access not within mapped region at address 0x30
==1075==    at 0x5ACBDF3: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.1)
==1075==    by 0x5ACC2DD: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.1)
==1075==    by 0x5ACC271: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.1)
==1075==    by 0x5ACC271: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.1)
==1075==    by 0x5ACD1F4: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.1)
==1075==    by 0x632B3E7: ??? (in /usr/lib/x86_64-linux-gnu/libgdk-3.so.0.2200.1)
==1075==    by 0x7BF0689: g_main_dispatch (gmain.c:3203)
==1075==    by 0x7BF0689: g_main_context_dispatch (gmain.c:3856)
==1075==    by 0x7BF0A3F: g_main_context_iterate.isra.29 (gmain.c:3929)
==1075==    by 0x7BF0AEB: g_main_context_iteration (gmain.c:3990)
==1075==    by 0x765D70C: g_application_run (gapplication.c:2381)
==1075==    by 0x42FE3E: main (nemo-main.c:104)


BTW, why do the libgtk debug symbols not show up? I have them installed.

> I don't know how much help I can be though, because nemo isn't crashing
> on my machine.

Sorry, I know it is strange, but it is the only computer where I see that,
and it is only nemo, all other programs run fine (so I believe I can 
rule out memory errors, espc since it is 100% reproducable)

All the best

Norbert

--
PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info
GPG: 0x860CDC13    fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13