With an r300 DRI checked out a couple of days ago I get a SEGV with the
backtrace below, I will try updating from CVS and looking at it more
closely later as I find some time...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 805425952 (LWP 6928)]
r300NewTextureObject
On Fri, 2006-04-14 at 10:38 +1000, Benjamin Herrenschmidt wrote:
With an r300 DRI checked out a couple of days ago I get a SEGV with the
backtrace below, I will try updating from CVS and looking at it more
closely later as I find some time...
Same with current CVS, will investigate later
On Fri, 2006-04-14 at 11:00 +1000, Benjamin Herrenschmidt wrote:
On Fri, 2006-04-14 at 10:38 +1000, Benjamin Herrenschmidt wrote:
With an r300 DRI checked out a couple of days ago I get a SEGV with the
backtrace below, I will try updating from CVS and looking at it more
closely later as I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benjamin Herrenschmidt wrote:
Ok, I got bitten by the build system again...
Checking out a fresh mesa source tree, doing a make linux-dri-ppc in it,
what hapens is that
- mesa bits are built using GL/internal/*.h includes from the source
On Thu, 2006-04-13 at 22:04 -0700, Ian Romanick wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benjamin Herrenschmidt wrote:
Ok, I got bitten by the build system again...
Checking out a fresh mesa source tree, doing a make linux-dri-ppc in it,
what hapens is that
- mesa
On Fri, 2006-04-14 at 15:15 +1000, Benjamin Herrenschmidt wrote:
Not sure at this point, but the problem ends up being ctx-DriverCtx at
a different offset
within GLcontext between mesa context.c and r300_tex.c.
Looks like to get the stuff built properly, one has to build first, make
