http://bugs.freedesktop.org/show_bug.cgi?id=15567
jasper <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
--- Comment #7 from jasper <[EMAIL PROTECTED]> 2008-07-07 16:27:12 PST ---
I've seen a similar backtrace with Mesa 6.5.2 (without dri). In that case it
was caused by a fragment shader trying to fetch texels from a texture unit that
didn't have any texture assigned to it.
I kluged around it with:
+ if (swrast->TextureSample[unit] == NULL)
+ {
+ _mesa_printf("%s: texture unit %d is NULL, ignoreing\n", __FUNCTION__,
+ unit);
+ color[0] = 1.0;
+ color[1] = 0.0;
+ color[2] = 0.0;
+ color[3] = 1.0;
+ return;
+ }
+
in fetch_texel in s_nvfragprog.c (the location of that function has changed in
newer sources).
Would be worth trying something like this patch to see if that helps.
if you have a core dump, or can reproduce the crash, then at the gdb prompt
typeing:
select 0
info frame
print unit
print swrast->TextureSample[unit]
and paste the results in here.
I don't know if xine's doing the same thing, can you get the actual fragment
program out of it?
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
