From: Ian Pilcher Subject: Heap corruption regression in 2.15.0 Date: Tue, 17 May 2011 23:17:01 -0500 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by gabe.freedesktop.org (Postfix) with ESMTP id A44C89E759 for ; Tue, 17 May 2011 21:17:15 -0700 (PDT) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QMYCA-0006NC-8f for intel-gfx@lists.freedesktop.org; Wed, 18 May 2011 06:17:14 +0200 Received: from pool-71-252-173-127.dllstx.fios.verizon.net ([71.252.173.127]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 18 May 2011 06:17:14 +0200 Received: from arequipeno by pool-71-252-173-127.dllstx.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 18 May 2011 06:17:14 +0200 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org With the recently pushed Fedora 15 update to 2.15.0, I'm getting a hard X hang every time I log out. gdb backtrace reveals that glibc is dead- locking trying to report a heap corruption: #0 __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:100 #1 0x00007fb07f8c7c11 in _L_lock_10461 () at malloc.c:6486 #2 0x00007fb07f8c59d7 in __libc_malloc (bytes=140396034138592) at malloc.c:3657 #3 0x00007fb07f8bb35d in __libc_message (do_abort=2, fmt=0x7fb07f9a6fb8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:137 #4 0x00007fb07f8c196a in malloc_printerr (action=3, str=0x7fb07f9a3f92 "corrupted double-linked list", ptr=) at malloc.c:6283 #5 0x00007fb07f8c1d48 in malloc_consolidate (av=0x7fb07fbe21e0) at malloc.c:5161 #6 0x00007fb07f8c2669 in malloc_consolidate (av=0x7fb07fbe21e0) at malloc.c:5115 #7 _int_free (av=0x7fb07fbe21e0, p=, have_lock=0) at malloc.c:5034 #8 0x000000351360c01f in FontFileFreeDir (dir=0x1fef3d0) at fontdir.c:166 #9 0x000000351360ce18 in FontFileFreeFPE (fpe=0x1fef360) at fontfile.c:139 #10 0x000000351360f89e in CatalogueUnrefFPEs (fpe=) at catalogue.c:116 #11 0x000000351360fe41 in CatalogueFreeFPE (fpe=0x1fb8f00) at catalogue.c:272 #12 0x000000000042f09d in FreeFPE (fpe=0x1fb8f00) at dixfonts.c:218 #13 FreeFPE (fpe=0x1fb8f00) at dixfonts.c:214 #14 0x000000000042f107 in FreeFontPath (list=0x1fb54b0, n=2, force=1) at dixfonts.c:1628 #15 0x0000000000432257 in FreeFonts () at dixfonts.c:1998 #16 0x0000000000422f1e in main (argc=, argv=0x7fff89fd3fb8, envp=) at main.c:329 This does not happen with the 2.14.0 package (verified by downgrading). Anyone have any ideas for potential suspect commits? Thanks! -- ======================================================================== Ian Pilcher arequipeno@gmail.com "If you're going to shift my paradigm ... at least buy me dinner first." ========================================================================