From: Chris Wilson <chris@chris-wilson.co.uk>
To: Ian Pilcher <arequipeno@gmail.com>, intel-gfx@lists.freedesktop.org
Subject: Re: Heap corruption regression in 2.15.0
Date: Wed, 18 May 2011 08:43:10 +0100 [thread overview]
Message-ID: <aefc95$6hdi@orsmga001.jf.intel.com> (raw)
In-Reply-To: <iqvh7u$djr$1@dough.gmane.org>
On Tue, 17 May 2011 23:17:01 -0500, Ian Pilcher <arequipeno@gmail.com> 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
next prev parent reply other threads:[~2011-05-18 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 4:17 Heap corruption regression in 2.15.0 Ian Pilcher
2011-05-18 7:43 ` Chris Wilson [this message]
2011-05-18 15:54 ` Ian Pilcher
2011-05-18 18:23 ` Ian Pilcher
2011-05-21 16:04 ` Ian Pilcher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='aefc95$6hdi@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=arequipeno@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.