Comment 6 for bug 328035
Revision history for this message
| Matt Zimmerman (mdz) wrote Re: *** glibc detected *** free(): invalid next size (fast) | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Bryce, I think it's significantly simpler than that.
This stack trace isn't being written out by the X server but by glibc (note the different formatting). glibc notices that the heap is corrupt while attempting to satisfy a free(3) call, prints out a backtrace to /dev/tty, and aborts the process with SIGABRT. The X server's own signal handler isn't involved here, and there's only one crash.
The main obstacle I face in trying to debug this properly is that my text consoles don't work. They show a corrupt screen with some blue lines. I don't know if this is a recurrence of bug 312677 or something new, but if it were fixed, I could run X from the console and see the backtrace printed by glibc to /dev/tty.