[ Please follow up to one list only, I suggest dri-devel ]
On Thu, 2007-02-01 at 20:08 +0200, Panagiotis Papadakos wrote:
My application sometimes crashes with the following message (most of the
times
when I run it with valgrind):
drmRadeonCmdBuffer: -22 (exiting)
And in dmesg I get the
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-02 08:29 ---
Created an attachment (id=10258)
-- (http://bugzilla.kernel.org/attachment.cgi?id=10258action=view)
Xorg.0.log for FC kernel 2.6.19-1.2917.fc7 [2.6.20rc7]
The kernel
http://bugzilla.kernel.org/show_bug.cgi?id=7767
--- Additional Comments From [EMAIL PROTECTED] 2007-02-02 08:39 ---
Created an attachment (id=10259)
-- (http://bugzilla.kernel.org/attachment.cgi?id=10259action=view)
Xorg.0.log for FC kernel 2.6.19-1.2917.fc7 [2.6.20rc7] using DRM
Well this patch is not correct since it leads to memory leaks, probably due to
succeeding calls to dri_interface-getDrawableInfo. So I created the attached
patch, but again valgrind warns for invalid reads.
Anyone understands why?
Thanks
P.S. Sorry but I am new to the code!
On Thursday 01
On Friday 02 February 2007 12:01, Michel Dänzer wrote:
Hmm, I think this could only happen with several file descriptors
using the same DRM context ID. Is your application multithreaded?
No, my application is not multithreaded.
This is using r300 driver and aiglx.
FWIW, does disabling
