Comment 7 for bug 328035

Revision history for this message
Matt Zimmerman (mdz) wrote : Re: *** glibc detected *** free(): invalid next size (fast)

My text consoles are now working again (still not sure what the root cause was). So I now have the X server attached with gdb, and when this happens next, I'll get a full backtrace.

However, this backtrace will only be for the free(3) which triggers the abort. If my guess is right, then the corruption is happening sometime earlier, and may be very difficult to track down. Does the X server play nicely with valgrind?