From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: Heap corruption regression in 2.15.0 Date: Wed, 18 May 2011 08:43:10 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by gabe.freedesktop.org (Postfix) with ESMTP id BB6199E74D for ; Wed, 18 May 2011 00:43:13 -0700 (PDT) In-Reply-To: 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: Ian Pilcher , intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Tue, 17 May 2011 23:17:01 -0500, Ian Pilcher wrote: > 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: What sort of tasks do you do during the sessions that encounter this corruption? Is it limited to a single chipset? When I valgrind, I tend to stick to the automated tests, i.e. those that I can run remotely and leave running, for the obvious reasons.... If you can narrow done the circumstances under which it occurs, I can then hopefully reproduce it and capture the error. Thanks, -Chris -- Chris Wilson, Intel Open Source Technology Centre