From: Ian Pilcher <arequipeno@gmail.com>
To: chris@chris-wilson.co.uk
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Heap corruption regression in 2.15.0
Date: Sat, 21 May 2011 11:04:08 -0500 [thread overview]
Message-ID: <4DD7E278.2000803@gmail.com> (raw)
In-Reply-To: <4DD40EB7.9010103@gmail.com>
On 05/18/2011 01:23 PM, Ian Pilcher wrote:
>
> It looks like the problematic commit is one of:
>
> e1ff5182304e00c0d392092069422cae7626cf8d Handle drawable/client
> destruction in pending swaps/flips
>
> 86f23f21ab57fcbc031bcd2b8f432a08ff4cc320 Skip client and drawable
> resource delete calls when deleting frame event
>
I have bugzilla'ed this at:
https://bugs.freedesktop.org/show_bug.cgi?id=37420
Any thoughts on how I can further debug this? It's gonna suck to be
stuck on 2.14.0 forever ...
--
========================================================================
Ian Pilcher arequipeno@gmail.com
"If you're going to shift my paradigm ... at least buy me dinner first."
========================================================================
prev parent reply other threads:[~2011-05-21 16:04 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
2011-05-18 15:54 ` Ian Pilcher
2011-05-18 18:23 ` Ian Pilcher
2011-05-21 16:04 ` Ian Pilcher [this message]
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=4DD7E278.2000803@gmail.com \
--to=arequipeno@gmail.com \
--cc=chris@chris-wilson.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox