Same issue here! Here is my backtrace after running window.Window()
#0 0xb7d13276 in glGetString () from /usr/lib/libGL.so
#1 0xb7d82107 in ffi_call_SYSV () at /build/buildd/python2.6-2.6.2/
Modules/_ctypes/libffi/src/x86/sysv.S:61
#2 0xb7d81f46 in ffi_call (cif=0x0, fn=0xb7d13270 <glGetString>,
rvalue=0x4, avalue=0xbf842430)
at /build/buildd/python2.6-2.6.2/Modules/_ctypes/libffi/src/x86/
ffi.c:213
#3 0xb7d7c64a in _CallProc (pProc=0xb7d13270 <glGetString>,
argtuple=0x9cfcf6c, flags=<value optimized out>,
argtypes=0xb79e702c, restype=0x9b96404, checker=0x0) at /build/
buildd/python2.6-2.6.2/Modules/_ctypes/callproc.c:815
#4 0xb7d73f49 in CFuncPtr_call (self=0xb79e577c, inargs=0x9cfcf6c,
kwds=0x0)
at /build/buildd/python2.6-2.6.2/Modules/_ctypes/_ctypes.c:3857
#5 0x0806111a in PyObject_Call (func=0xb79e577c, arg=0x9cfcf6c,
kw=0x0) at ../Objects/abstract.c:2492
#6 0x080dcfea in PyEval_EvalFrameEx (f=0xa0dd124, throwflag=0) at ../
Python/ceval.c:3917
#7 0x080df587 in PyEval_EvalFrameEx (f=0xa0dce24, throwflag=0) at ../
Python/ceval.c:3792
#8 0x080df587 in PyEval_EvalFrameEx (f=0xa0dcb3c, throwflag=0) at ../
Python/ceval.c:3792
#9 0x080df587 in PyEval_EvalFrameEx (f=0xa0d5784, throwflag=0) at ../
Python/ceval.c:3792
#10 0x080df587 in PyEval_EvalFrameEx (f=0x9c36134, throwflag=0) at ../
Python/ceval.c:3792
#11 0x080e00b8 in PyEval_EvalCodeEx (co=0xb7e060f8,
globals=0xb7d2eb54, locals=0x0, args=0xb77e2598, argcount=1,
kws=0x9c35720, kwcount=3, defs=0xb7881e90, defcount=12,
closure=0x0) at ../Python/ceval.c:2968
#12 0x081688c6 in function_call (func=0xb77d9ca4, arg=0xb77e258c,
kw=0x9d7e8ac) at ../Objects/funcobject.c:524
#13 0x0806111a in PyObject_Call (func=0xb77d9ca4, arg=0xb77e258c,
kw=0x9d7e8ac) at ../Objects/abstract.c:2492
#14 0x080db1cd in PyEval_EvalFrameEx (f=0x9ca0384, throwflag=0) at ../
Python/ceval.c:4005
#15 0x080e00b8 in PyEval_EvalCodeEx (co=0xb77e1e30,
globals=0xb787ca44, locals=0x0, args=0xb77e2558, argcount=1,
kws=0x9c98d98, kwcount=3, defs=0x0, defcount=0, closure=0x0) at ../
Python/ceval.c:2968
#16 0x081688c6 in function_call (func=0x9d3d3e4, arg=0xb77e254c,
kw=0x9d7e824) at ../Objects/funcobject.c:524
#17 0x0806111a in PyObject_Call (func=0x9d3d3e4, arg=0xb77e254c,
kw=0x9d7e824) at ../Objects/abstract.c:2492
#18 0x0806801a in instancemethod_call (func=0x9d3d3e4, arg=0xb77e254c,
kw=0x9d7e824) at ../Objects/classobject.c:2579
#19 0x0806111a in PyObject_Call (func=0xb77cc6e4, arg=0xb7e1102c,
kw=0x9d7e824) at ../Objects/abstract.c:2492
#20 0x080b2c8e in slot_tp_init (self=0xb77e288c, args=0xb7e1102c,
kwds=0x9d7e824) at ../Objects/typeobject.c:5632
#21 0x080ab6c1 in type_call (type=0x9ca993c, args=0xb7e1102c,
kwds=0x9d7e824) at ../Objects/typeobject.c:745
#22 0x0806111a in PyObject_Call (func=0x9ca993c, arg=0xb7e1102c,
kw=0x9d7e824) at ../Objects/abstract.c:2492
#23 0x080dcfea in PyEval_EvalFrameEx (f=0x9d17304, throwflag=0) at ../
Python/ceval.c:3917
#24 0x080df587 in PyEval_EvalFrameEx (f=0x9b824e4, throwflag=0) at ../
Python/ceval.c:3792
#25 0x080e00b8 in PyEval_EvalCodeEx (co=0xb7d349b0,
globals=0xb7d2eb54, locals=0xb7d2eb54, args=0x0, argcount=0, kws=0x0,
kwcount=0, defs=0x0, defcount=0, closure=0x0) at ../Python/ceval.c:
2968
#26 0x080e0217 in PyEval_EvalCode (co=0xb7d349b0, globals=0xb7d2eb54,
locals=0xb7d2eb54) at ../Python/ceval.c:522
#27 0x080f21a9 in PyImport_ExecCodeModuleEx (name=0xbf847237
"pyglet.window", co=0xb7d349b0,
pathname=0xbf844127 "/var/lib/python-support/python2.6/pyglet/
window/__init__.pyc") at ../Python/import.c:680
#28 0x080f301d in load_source_module (name=0xbf847237
"pyglet.window",
pathname=0xbf844127 "/var/lib/python-support/python2.6/pyglet/
window/__init__.pyc", fp=<value optimized out>)
at ../Python/import.c:1016
#29 0x080f3827 in load_package (name=0xbf847237 "pyglet.window",
pathname=<value optimized out>) at ../Python/import.c:1072
#30 0x080f3e19 in import_submodule (mod=0xb7e11464, subname=0xbf84723e
"window", fullname=0xbf847237 "pyglet.window")
at ../Python/import.c:2590
#31 0x080f40ba in load_next (mod=0xb7e11464, altmod=0xb7e11464,
p_name=<value optimized out>,
buf=0xbf847237 "pyglet.window", p_buflen=0xbf847230) at ../Python/
import.c:2410
#32 0x080f46e0 in import_module_level (name=0x0, globals=<value
optimized out>, locals=<value optimized out>, fromlist=0x0,
level=-1) at ../Python/import.c:2139
#33 0x080f4c52 in PyImport_ImportModuleLevel (name=0xb7e02a0c
"pyglet.window", globals=0x0, locals=0x0, fromlist=0x0,
level=-1) at ../Python/import.c:2183
#34 0x080d8464 in builtin___import__ (self=0x0, args=0xb7dffccc,
kwds=0x0) at ../Python/bltinmodule.c:48
#35 0x080de562 in PyEval_EvalFrameEx (f=0x9b65424, throwflag=0) at ../
Python/ceval.c:3706
#36 0x080e00b8 in PyEval_EvalCodeEx (co=0xb7df7338,
globals=0xb7df879c, locals=0x0, args=0xb7dff2f8, argcount=2, kws=0x0,
kwcount=0, defs=0x0, defcount=0, closure=0x0) at ../Python/ceval.c:
2968
#37 0x081687df in function_call (func=0xb7d2f144, arg=0xb7dff2ec,
kw=0x0) at ../Objects/funcobject.c:524
#38 0x0806111a in PyObject_Call (func=0xb7d2f144, arg=0xb7dff2ec,
kw=0x0) at ../Objects/abstract.c:2492
#39 0x0806801a in instancemethod_call (func=0xb7d2f144,
arg=0xb7dff2ec, kw=0x0) at ../Objects/classobject.c:2579
#40 0x08065b21 in PyObject_CallFunctionObjArgs (callable=0xb7de0fa4)
at ../Objects/abstract.c:2492
#41 0x080b0d44 in slot_tp_getattr_hook (self=0xb7e034ec,
name=0xb7dff1a0) at ../Objects/typeobject.c:5410
#42 0x080dccc6 in PyEval_EvalFrameEx (f=0x9b00ccc, throwflag=0) at ../
Python/ceval.c:2059
#43 0x080e00b8 in PyEval_EvalCodeEx (co=0xb7e3f608,
globals=0xb7e350b4, locals=0xb7e350b4, args=0x0, argcount=0, kws=0x0,
kwcount=0, defs=0x0, defcount=0, closure=0x0) at ../Python/ceval.c:
2968
#44 0x080e0217 in PyEval_EvalCode (co=0xb7e3f608, globals=0xb7e350b4,
locals=0xb7e350b4) at ../Python/ceval.c:522
#45 0x080fe0e1 in PyRun_FileExFlags (fp=0x9b06fa8, filename=0xbf8497b7
"pyglet_example.py", start=257, globals=0xb7e350b4,
locals=0xb7e350b4, closeit=1, flags=0xbf848dd8) at ../Python/
pythonrun.c:1335
#46 0x080fe43a in PyRun_SimpleFileExFlags (fp=0x9b06fa8,
filename=0xbf8497b7 "pyglet_example.py", closeit=1,
flags=0xbf848dd8) at ../Python/pythonrun.c:931
#47 0x0805c882 in Py_Main (argc=1, argv=0xbf848ea4) at ../Modules/
main.c:599
#48 0x0805b972 in main (argc=Cannot access memory at address 0x0
) at ../Modules/python.c:23
I am also running Jaunty, graphics:
ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 02)
Any help would be greatly appreciated, I am desperately trying to use
pyglet!
On May 4, 6:57 am, Jonathan Hartley <[email protected]> wrote:
> Hey Thomas,
>
> Thanks for the info.
>
> I don't *think* that pyglet is using glut functions to manage windows
> - looking at the pyglet source, it seems to call directly into X
> windows libraries using ctypes instead. I don't know whether Glut
> method calls and X lib calls would, under the covers, both hit the
> same speedbump, or whether these are two separate seg faults.
>
> Clearly though, the common factor is the ATI drivers under Jaunty. I
> have since found other things that are flaky here. Some games work
> fine, others (eg., BZFlag) lock up after a fraction of a second. In
> fact, now I come to write this, maybe there's a helpful bug I could
> file for the ati driver project. I'll go over there and see whether
> their existing bug reports seem to have it all covered.
>
> I considered downgrading from Jaunty back to Intrepid, but there is no
> formal migration path, so it would be a full reinstall. So I'm going
> to use my Nvidia desktop machine to develop on while the install ticks
> along, and hope the open source ATI drivers improve the situation in
> the not-too-distant-future. Have also upped the priority on a
> replacement laptop with Nvidia on-board, but that won't happen
> immediately.
>
> Thanks all,
>
> Jonathan
>
> On May 4, 10:04 am, Thomas <[email protected]> wrote:
>
> > hi, i have the same issue using the ati driver with jaunty.
> > on launchpad, they mentioned several times that this can be a problem
> > with the glutCreateWindow() function, in particular it has to be
> > called before glutInitDisplayMode().
>
> > here is an answer of an user from the launchpad issue tracker:
> > [quote]
> > Yes, making the code look like this, completely resolves this
> > segmentation fault problem:
>
> > GLUT.glutInit(sys.argv)
> > GLUT.glutCreateWindow('foobar') # required to be a line before
> > glutInitDisplay
> > GLUT.glutInitDisplayMode(GLUT.GLUT_RGBA | GLUT.GLUT_DOUBLE)
> > [/quote]
>
> > my understanding of the pyglet code is very poor right now, but i will
> > try to find out if this is the source of the problem..
>
> > On 1 Mai, 14:36, Jonathan Hartley <[email protected]> wrote:
>
> > > > It's not clear to me whether the seg fault you're reporting happens
> > > > with the "fglrx" or "ati" driver (or both?)
>
> > > Beg your pardon.
> > > The 'fglrx' driver doesn't work at all since I upgraded (I am not
> > > alone in this.)
> > > The segfault when using pyglet occurs using the 'ati' driver (am I
> > > alone in this?)
>
> > > > Stop trying to use accelerated ATI under Linux?
>
> > > Sincerely considering it.
>
> > > Thanks.
>
> > > On May 1, 1:39 am, Richard Jones <[email protected]> wrote:
>
> > > > On 01/05/2009, at 9:54 AM, Jonathan Hartley wrote:
>
> > > > > I upgraded to Ubuntu Jaunty (9.04) and now 'from pyglet.window import
> > > > > Window' gives me a seg fault.
>
> > > > > I have an ATI card (ohdear), a Radeon X1400.
>
> > > > > I tried to use ATI's proprietary 'fglrx' driver at first, but that
> > > > > apparently has problems under Jaunty, and only produces garbage on-
> > > > > screen for me, so I've fallen back to the open source 'ati' driver,
> > > > > which apparently works, reportedly is stable, but has mediochre 3D
> > > > > performance.
>
> > > > It's not clear to me whether the seg fault you're reporting happens
> > > > with the "fglrx" or "ati" driver (or both?)
>
> > > > > Anyone got any suggestions of things I might try?
>
> > > > Stop trying to use accelerated ATI under Linux?
>
> > > > Richard
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pyglet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
