[Visualpython-users] Re: Segmentation fault - gdb python

On Thu, 11 Jan 2001, Nils Wagner wrote:

> Hi Ari,
> 
> Please find enclosed the messages of gdb running python
> 
> This GDB was configured as "i386-suse-linux"...(no debugging symbols 
> found)...
> (gdb) run
> Starting program: /usr/local/bin/python
> Python 1.5.2 (#1, Jul 29 2000, 14:28:37)  [GCC 2.95.2 19991024 (release)] on 
> lin
> ux2
> Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
> >>>from visual import *
> Visual-2000-11-26
> >>>sphere()
> [New Thread 1191 (manager thread)]
> [New Thread 1190 (initial thread)]
> [New Thread 1192]
> [Switching to Thread 1192]
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x408c90a7 in pioOutLong () from /usr/lib/libglide2x.so
> (gdb) backtrace
> #0  0x408c90a7 in pioOutLong () from /usr/lib/libglide2x.so
> (gdb)
> 
Aha :)

This is Glide crashing.

We've seen similar stuff where we've gotten Mesa to crash. And it's not
necessarily entirely Glide's fault; we may be doing something inadvertently
evil that makes Glide unhappy.

Can you check 2 things:

1) Do other GL programs work rigt on this computer? (i.e. is Glide happy with
other stuff? The crash seems to be coming at a low level, judging by the
nonexistent callstack).

2) Can you try this with software GL? i.e. reconfigure your machine with a
software version of Mesa, and try that. We've been running on software and on
nVidia hardware on Linux; i'm not sure we've tried it against Mesa/Glide
(unless ... Dave, does marvin have a 3dfx and hardware GL configured in
Linux?).

I'm betting it will work if you use software GL ...




ari