On 06/02/2014 09:22 PM, Kenneth Graunke wrote:
On Monday, June 02, 2014 07:44:15 PM Benjamin Bellec wrote:
[snip]
The "canary error" on Google points to a previously closed bug from
glsl-compiler :
https://bugs.freedesktop.org/show_bug.cgi?id=58039
It's probably unrelated - failing the canary check basically just means you
botched your memory management. Or, more specifically, you passed a non-
ralloc'd pointer to a ralloc function.
This was the case and thanks to Benjamin's backtrace it's fixed now
(will send v2 for patch 18). It seems there are some other issues with
gallium though, I'll need to get myself a test environment to hunt these
down.
While rebasing my patches I noticed that L4D2 is not so good test case
anymore though as it is broken with Mesa master :/
https://bugs.freedesktop.org/show_bug.cgi?id=79616
I suppose it might be more ctx/mem_ctx confusion.
Valgrind can usually track these problems down.
--Ken
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
