Bug#752157: gdm-session-worker segfaults after entering the password

[Simon McVittie]

On 20/06/14 05:17, Marco d'Itri wrote:
> #0  _int_malloc (av=av at entry=0xf7299420 <main_arena>, bytes=bytes at entry=100) at malloc.c:3489
> #1  0xf7168521 in __GI___libc_malloc (bytes=bytes at entry=100) at malloc.c:2891
> #2  0xf71eae91 in __GI___vasprintf_chk (result_ptr=0xffdc6e3c, flags=1, format=0x806e7a8 "GdmSessionWorker: trying to get updated username", args=0xffdc6f1c "Lo\334\377") at vasprintf_chk.c:48
> #3  0xf73e1aba in g_vasprintf () from /lib/i386-linux-gnu/libglib-2.0.so.0
> #4  0xf73bb323 in g_strdup_vprintf () from /lib/i386-linux-gnu/libglib-2.0.so.0
> #5  0xf73a42df in g_logv () from /lib/i386-linux-gnu/libglib-2.0.so.0
> #6  0xf73a4673 in g_log () from /lib/i386-linux-gnu/libglib-2.0.so.0
> #7  0x08055d43 in ?? ()
> #8  0xf7663927 in pam_vprompt () from /lib/i386-linux-gnu/libpam.so.0
> #9  0xf7663adb in pam_prompt () from /lib/i386-linux-gnu/libpam.so.0

This looks like fallout from previous memory corruption, so the
interesting stack trace would be the one where the memory corruption
occurred, not the one where the crash happens. Can you reproduce this
under valgrind, electric-fence, MALLOC_CHECK_=3 or similar?

> ii  libsystemd-daemon0                           208-1
> ii  libsystemd-id128-0                           204-10

Probably unrelated, but I notice those don't match.

    S