<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - dungeon defenders crashes after vbo_exec_DrawRangeElements call" href="https://bugs.freedesktop.org/show_bug.cgi?id=89084#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - dungeon defenders crashes after vbo_exec_DrawRangeElements call" href="https://bugs.freedesktop.org/show_bug.cgi?id=89084">bug 89084</a> from <a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> Eero Tamminen</a> <pre>(In reply to Karol Herbst from <a href="show_bug.cgi?id=89084#c3">comment #3</a>) > Created <a href="attachment.cgi?id=113464" name="attach_113464" title="valgrind output">attachment 113464</a> <a href="attachment.cgi?id=113464&action=edit" title="valgrind output">[details]</a> > valgrind output Thanks! > sadly I can't debug further with the steam version, so I have to check if I > also have a non-steam version somwhere. But there are some invalid write of > size 4 from mesa, which I think may libsdl2 or mesa bugs itself or maybe it > should be that way. This could be Valgrind not knowing where the memory came from. Only if your libdrm library is built with Valgrind devel files present in the system, it will annotate the memory it returns from kernel for Valgrind. On Ubuntu 14.10, the necessary files come with "valgrind" package, but libdrm needs to be (re-)build after that is installed. Another issue is that for Valgrind backtraces to be useful, Mesa debug symbols are needed, so that we can see where (which source file/line) the Valgrind warnings are coming from. Could you fix those issues and attach updated Valgrind output?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>