Le 19/01/2009 08:52, Florian Echtler a écrit :
Apologies. I misread the original message. For whatever reason (blame
it on being Friday), I thought you were replacing glXMakeCurrent with
glXMakeContextCurrent, not the other way around.
Never mind, I was starting to get confused, too.. :-)
Florian Echtler wrote:
- It calls a GLX 1.3 function on a system that doesn't support GLX 1.3.
Could you check for GLX 1.3 at compile time? I suppose not, but maybe
there is a way?
The GLX version is a property of the X server. There's no way that you
can check this until the client has
On Sat, 2009-01-17 at 11:28 +0100, Florian Echtler wrote:
The bug causes a segfault in libGL.so, though even with debug info
enabled, I can't see the exact location. However, I can work around the
bug when, in freeglut, I replace
Why would you do that? There is no improvement to freeglut
Apologies. I misread the original message. For whatever reason (blame
it on being Friday), I thought you were replacing glXMakeCurrent with
glXMakeContextCurrent, not the other way around.
Never mind, I was starting to get confused, too.. :-)
There are two bugs in freeglut:
- It calls a
The bug causes a segfault in libGL.so, though even with debug info
enabled, I can't see the exact location. However, I can work around the
bug when, in freeglut, I replace
Why would you do that? There is no improvement to freeglut and no
benefit to its users. If the read drawable and the
The bug causes a segfault in libGL.so, though even with debug info
enabled, I can't see the exact location. However, I can work around the
bug when, in freeglut, I replace
Why would you do that? There is no improvement to freeglut and no
benefit to its users. If the read drawable and
Hello everyone,
I've found a bug in the interaction between freeglut and mesa. This
applies to mesa 7.2 and 7.3-rc2 and occurs both with freeglut-current
and freeglut-2.6.0-rc1. I'm using the radeon driver on a Radeon Mobility
X1400.
The bug causes a segfault in libGL.so, though even with debug
According to the GLX spec, these two calls should be equivalent.
However, the first one causes a segfault, the second one doesn't. So I
suppose this is really a bug in mesa somewhere.
No. The former is only supported as of GLX 1.3, but your setup only
supports GLX 1.2.
I'm sorry, I just
On Fri, 2009-01-16 at 14:57 +0100, Florian Echtler wrote:
According to the GLX spec, these two calls should be equivalent.
However, the first one causes a segfault, the second one doesn't. So I
suppose this is really a bug in mesa somewhere.
No. The former is only supported as of GLX
On Fri, 2009-01-16 at 12:14 +0100, Florian Echtler wrote:
I've found a bug in the interaction between freeglut and mesa. This
applies to mesa 7.2 and 7.3-rc2 and occurs both with freeglut-current
and freeglut-2.6.0-rc1. I'm using the radeon driver on a Radeon Mobility
X1400.
The bug causes
10 matches
Mail list logo
