On Jun 20, Simon McVittie <[email protected]> wrote: > This looks like fallout from previous memory corruption, so the It is 100% reproducible.
> 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? Is there an easier way to do this than replacing the gdm-session-worker binary with a wrapper script and starting gdm again? -- ciao, Marco
signature.asc
Description: Digital signature
