Created attachment 32489 [details] A log of the gdb session with backtrace and shader source After rebuilding Mesa (with debugging symbols) from the git master branch (at revision 6f498a7eff26dc055c0a1f75ce3102aa4a1a0141 ), I am unable to run a game that utilizes 3d accel and shaders that (mostly) worked previously. This particular issue did not appear to affect me in my previous build (which was also from git master branch built around 2009-12-24 or so, I believe). I am running Gentoo ~amd64. My graphics card is a Radeon X850. The bug manifests with the following versions of software: libdrm commit 5dbc1b333b85695735dc5b484372758b9979b693 mesa commit 6f498a7eff26dc055c0a1f75ce3102aa4a1a0141 xf86-video-ati commit 48aa5064aff4b9adf768e480df2312d4375e9c40 nvidia-cg-toolkit version 2.2.0010, build date Sep 29 2009 16:29:47. CrystalSpace Revision: 33500 Planeshift Revision: 5164 I have attached a gdb session which includes a backtrace and (I believe) the complete source of the shader that causes mesa to hiccup, and the full command arguments that were passed to cgc. I am willing to provide further information if required. Note that this shader does not seem to cause problems for other players of this game on other platforms, but that this does not necessarily mean it is not, itself, buggy or problematic.
Created attachment 32492 [details] The offending Cg source, extracted from gdb output and with some escape sequences converted It was suggested to me to make the shader's source a bit more readable/accessible, so here it is with \n, \t, and \\ converted into newlines, tabs, and \, repsectively.
Created attachment 32494 [details] Problematic ARB source code
Created attachment 32495 [details] Cg source Same data as attachment 32492 [details], but with fixed MIME type
I can't reproduce this. I forced the parser to call the yyerror() function where your gdb log indicated. I don't get a segfault in vfprintf() or strlen(). Could you try recompiling Mesa for debug (-g) and retesting?
Brian, since I've been using Gentoo's portage system to build Mesa, I'm not sure how to give it specific switches, like -g, for compiling. I was under the impression that I was building Mesa with separate debugging information split off in its own file (Portage's splitdebug feature and the debug USE flag), so I'm also not entirely sure what the key difference you're after is, either. How do you suggest I proceed?
After recompiling (once with Portage's nostrip feature, then again with splitdebug) the latest code, I'm no longer able to reproduce the issue either. I guess the bug should be closed, since nobody seemed sure what was causing it in the first place.
Closing.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.