[visionegg] Re: New User, Seg Fault
- From: asif.ladak@xxxxxxxxxxxxxxxxxxxxxxx
- To: visionegg@xxxxxxxxxxxxx
- Date: Thu, 18 Sep 2003 11:26:05 -0400
Andrew,
>>>> Pygame Parachute Traceback:
>>>> File
>>>> "C:\Python22\Lib\site-packages\VisionEgg\PlatformDependent.py",
>>>> line 192, in sync_swap_with_vbl_post_gl_init
>>>> Fatal Python error: (pygame parachute) Segmentation Fault
>>>
>>
>> I turned off the option to synchronize buffer swaps. This had no
>> noticeable effect.
>
>Darn -- this means the error message above has little correlation to
>the error and will make it difficult to track down. Something is
>crashing at the C level (not in the Python interpreter, where we'd get
>a nice error message). Perhaps a required library started a thread
>which crashes, bringing down the whole app. Just to check, did you
>install the exact versions of the libraries as listed on the VE Windows
>install page?
Yes. I didn't even go to the linked websites; just downloaded them
straight from the link on that page.
>My immediate, unfounded suspicion falls on Tkinter (the GUI
>environment). Try turning it off by inserting the following into the
>beginning of the demo script (before the create_default_screen() call):
>
>import VisionEgg
>VisionEgg.config.VISIONEGG_GUI_INIT=0
>
This suppressed the GUI console, and the output stopped short of the pygame
parachute traceback quoted at the top. In the following output,
grating_ASIF_BK.py is the original code, and grating.py has the above two
lines inserted:
----BEGIN original code----
C:\visionegg\visionegg-0.9.5b3\demo>python grating_ASIF_BK.py
2003-09-18 10:45:00,577 (1640) INFO: Script grating_ASIF_BK.py started
Vision Egg 0.9.5b3 with process id 1640.
2003-09-18 10:45:04,493 (1640) INFO: Requesting window 640 x 480 32 bpp (8
8 8 0 RGBA).
(sent using deprecated VisionEgg.Core.Message class)
2003-09-18 10:45:04,554 (1640) INFO: OpenGL 1.3.0 - Build 4.14.10.3619,
Intel Brookdale-G, Intel
(sent using deprecated VisionEgg.Core.Message class)
2003-09-18 10:45:04,554 (1640) INFO: Video system reports 32 bpp (8 8 8 8
RGBA).
(sent using deprecated VisionEgg.Core.Message class)
Pygame Parachute Traceback:
File "C:\Python22\Lib\site-packages\VisionEgg\PlatformDependent.py", line
192, in sync_swap_with_vbl_post_gl_init
Fatal Python error: (pygame parachute) Segmentation Fault
This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.
----END----
----BEGIN modified code----
C:\visionegg\visionegg-0.9.5b3\demo>python grating.py
2003-09-18 10:45:20,343 (2372) INFO: Script grating.py started Vision Egg
0.9.5b3 with process id 23
72.
2003-09-18 10:45:20,485 (2372) INFO: Requesting window 640 x 480 32 bpp (8
8 8 0 RGBA).
(sent using deprecated VisionEgg.Core.Message class)
2003-09-18 10:45:20,547 (2372) INFO: OpenGL 1.3.0 - Build 4.14.10.3619,
Intel Brookdale-G, Intel
(sent using deprecated VisionEgg.Core.Message class)
2003-09-18 10:45:20,547 (2372) INFO: Video system reports 32 bpp (8 8 8 8
RGBA).
(sent using deprecated VisionEgg.Core.Message class)
C:\visionegg\visionegg-0.9.5b3\demo>
----END----
>It could be a PyOpenGL problem. Try running a few demos in
>c:\Python22\Lib\site-packages\OpenGL/Demo.
Most of these from what I tested worked fine. /Tom/fog.py and /Tom/Logo.py
didn't work. The rest seemed to work fine.
>Also, try running
>c:\Python22\Lib\site-packages\VisionEgg\test\opengl_info.py from the
>command line so you can see the results. Also, the conform.py test in
>there turns off Tkinter and tests lots of things, so it's worth a test.)
Um, I don't have a test folder in this directory. . .
I found these files under c:\visionegg\visionegg-0.9.5b3\test\
conform.py didn't seem to work -- see below.
---BEGIN output for opengl_info.py---
C:\visionegg\visionegg-0.9.5b3\test>python opengl_info.py
Initializing graphics at 640 x 480 ( 0 bpp ).
OpenGL information returned from OpenGL drivers:
GL_VENDOR = Intel
GL_RENDERER = Intel Brookdale-G
GL_VERSION = 1.3.0 - Build 4.14.10.3619
GL_EXTENSIONS =
GL_ARB_multitexture
GL_ARB_texture_border_clamp
GL_ARB_texture_compression
GL_ARB_texture_cube_map
GL_ARB_texture_env_add
GL_ARB_texture_env_combine
GL_ARB_texture_env_dot3
GL_ARB_texture_env_crossbar
GL_ARB_transpose_matrix
GL_EXT_abgr
GL_EXT_bgra
GL_EXT_blend_color
GL_EXT_blend_func_separate
GL_EXT_blend_minmax
GL_EXT_blend_subtract
GL_EXT_clip_volume_hint
GL_EXT_compiled_vertex_array
GL_EXT_cull_vertex
GL_EXT_fog_coord
GL_EXT_packed_pixels
GL_EXT_packed_pixels_12
GL_EXT_rescale_normal
GL_EXT_secondary_color
GL_EXT_separate_specular_color
GL_EXT_stencil_wrap
GL_EXT_texture_compression_s3tc
GL_EXT_texture_env_add
GL_EXT_texture_env_combine
GL_EXT_texture_filter_anisotropic
GL_3DFX_texture_compression_FXT1
GL_IBM_texture_mirrored_repeat
GL_NV_texgen_reflection
GL_WIN_swap_hint
C:\visionegg\visionegg-0.9.5b3\test>
---END---
---BEGIN conform.py---
C:\visionegg\visionegg-0.9.5b3\test>python conform.py
2003-09-18 11:13:17,381 (1604) INFO: Script conform.py started Vision Egg
0.9.5b3 with process id 16
04.
2003-09-18 11:13:17,600 (1604) INFO: Requesting window 512 x 512 32 bpp (8
8 8 0 RGBA).
(sent using deprecated VisionEgg.Core.Message class)
2003-09-18 11:13:17,662 (1604) INFO: OpenGL 1.3.0 - Build 4.14.10.3619,
Intel Brookdale-G, Intel
(sent using deprecated VisionEgg.Core.Message class)
2003-09-18 11:13:17,662 (1604) INFO: Video system reports 32 bpp (8 8 8 8
RGBA).
(sent using deprecated VisionEgg.Core.Message class)
C:\visionegg\visionegg-0.9.5b3\test>
---END---
>It could be a pygame/SDL problem. Try the flames_pygame.py demo (in
>the standard VE demos), which uses pygame but not OpenGL.
>
>Please let us know what you find!
The GUI console did not come up for this like it did for the other VE
demos.
---BEGIN flames_pygame.py---
C:\visionegg\visionegg-0.9.5b3\demo>python flames_pygame.py
2003-09-18 11:16:24,006 (2644) INFO: Script flames_pygame.py started Vision
Egg 0.9.5b3 with process
id 2644.
536870912
Traceback (most recent call last):
File "flames_pygame.py", line 139, in ?
if __name__ == '__main__': main()
File "flames_pygame.py", line 69, in main
blitdouble(screen, flame, doubleflame)
File "flames_pygame.py", line 135, in blitdouble
blit_array(screen, doubleflame)
ValueError: unsupported datatype for array
---END---
>You're right -- this is not the problem. Also, now that I know this is
>your "default" drive, I think it can safely be said that this is the
>desired behavior for os.path.expanduser('~'). A bit of history on this:
>it is often useful for Vision Egg to be able to write configuration
>files. Operating systems other than Windows don't let apps just write
>files into system directories (and there must be some way to get
>Windows to act this way, too), so the challenge was to find a
>(cross-platform) way of allowing non-privileged users to save files. I
>don't know what the Windows standard for this is (if it exists), but I
>thought the above method was probably best -- rely on Python to do the
>Right Thing. So, it's actually comforting that this is your default
>drive. The question is whether you, as the user, feel this is the right
>place for the Vision Egg to save user-specific configuration files.
>(And also whether other Windows users would agree with you.)
Works for me. It's probably a good thing, because I don't have access to
the entirety of my local drive, anyway. So placing files in say C:\Program
Files\ is not allowed -- (I actually had to call IT to have them remotely
log into my machine and update my video driver because the installer for it
wanted to create a c:\program files\installshield directory, which requires
Admin privileges.)
Well I have not a clue as to the implications of the output I have passed
on to you, so I guess I shall just wait.
--
Asif Ladak
=====================================The Vision Egg mailing list
Archives: //www.freelists.org/archives/visionegg
Website: http://www.visionegg.org/mailinglist.html
Other related posts:
- » [visionegg] New User, Seg Fault
- » [visionegg] New User, Seg Fault
- » [visionegg] Re: New User, Seg Fault
- » [visionegg] Re: New User, Seg Fault
- » [visionegg] Re: New User, Seg Fault
- » [visionegg] Re: New User, Seg Fault
- » [visionegg] Re: New User, Seg Fault
- » [visionegg] Re: New User, Seg Fault
- » [visionegg] Re: New User, Seg Fault
- » [visionegg] Re: New User, Seg Fault
