[Openparsec-devel] Segment violation with parsec-client

[<Sa...@t-...>]

As the old 0197-LANTEST version did not work any longer with  XF86 4.3, and my 
children still wanted to play parsec, I decided to wrap my own version 
binaries. I downloaded the sourcecode from CVS and after struggling with some 
compilation problems ( ##-operator and audiolib) I got a working client and 
server executable. Starting the client ( parsec executable) proceeds normally 
loading different objects but coredumps after printing following:

	GL_SGIS_texture_lod
	Creating OpenGL context:
	Color buffer at 16 bits.
	Depth buffer at 16 bits.

The executable is started with 
--windowed --noflipsync --vidmode 640x480x16

Using gdb gives me callstack:
(gdb) info stack
#0  0x4005ef17 in XQueryExtension () from /usr/X11R6/lib/libX11.so.6
#1  0x40053c7b in XInitExtension () from /usr/X11R6/lib/libX11.so.6
#2  0x40025ad0 in XextAddDisplay () from /usr/X11R6/lib/libXext.so.6
#3  0x4038151f in __glXFindDisplay () from /usr/lib/libGL.so
#4  0x40381bca in __glXInitialize () from /usr/lib/libGL.so
#5  0x40381e2f in __glXSetupForCommand () from /usr/lib/libGL.so
#6  0x40382234 in glXMakeCurrent () from /usr/lib/libGL.so


I run 
XFree86-server-4.3.0-15
XFree86-GLX-4.3.0-15

mesasoft-5.0-62
mesaglu-5.0-62
mesaglut-5.0-62
mesa-5.0-62
mesaglut-devel-5.0-62
mesaglu-devel-5.0-62
mesa-devel-5.0-62

Now, the question is, whether this is an X11 and GL-library problem or 
something special with PARSEC. I noticed in this mail-list that there were 
also some other persons experiencing segment violation - unfortunately they 
did not enclose callstack to be compared


Any ideas...

regards

Risto Sainio