visualpython-users

[Visualpython-users] Re: Linux : segmentation faults

[Lew R. <lr...@ur...>]

Jonathan Brandmeyer wrote:

> Uh-oh.  Yea, it sounds familiar.  I'm assuming that you have a laptop. 
> Do you by chance have a Pentium M processor in it (not a Pentium 3-M or
> Pentium 4-M)?

Yep. I've got a Dell Latitude D600 with a Pentium M processor.

> Please run one of the VPython programs that crashes in GDB (the GNU
> Debugger) by following these instructions, and send me the console
> output from the entire session.  I'm hoping that setting MESA_DEBUG=1 in
> the environment will produce something useful, but it might not.
> 

OK. Here's the initial output and bactrace from gdb:

--
MMX cpu detected.
Testing OS support for SSE... yes.
Testing OS support for SSE unmasked exceptions...
Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 1441717168 (LWP 11823)]
0x56094c94 in _mesa_test_os_sse_exception_support ()
    from /usr/X11R6/lib/modules/dri/r200_dri.so
(gdb) bt
#0  0x56094c94 in _mesa_test_os_sse_exception_support ()
    from /usr/X11R6/lib/modules/dri/r200_dri.so
#1  0x56094a21 in check_os_sse_support ()
    from /usr/X11R6/lib/modules/dri/r200_dri.so
#2  0x56094b40 in _mesa_init_all_x86_transform_asm ()
    from /usr/X11R6/lib/modules/dri/r200_dri.so
#3  0x56013beb in _math_init () from /usr/X11R6/lib/modules/dri/r200_dri.so
#4  0x55f989fa in one_time_init ()
    from /usr/X11R6/lib/modules/dri/r200_dri.so
#5  0x55f9abd4 in _mesa_initialize_context ()
    from /usr/X11R6/lib/modules/dri/r200_dri.so
#6  0x55f9b689 in _mesa_create_context ()
    from /usr/X11R6/lib/modules/dri/r200_dri.so
#7  0x5609a646 in r200CreateContext ()
    from /usr/X11R6/lib/modules/dri/r200_dri.so
#8  0x55f867f0 in driCreateContext ()
    from /usr/X11R6/lib/modules/dri/r200_dri.so
#9  0x0092a5da in _glthread_SetTSD () from /usr/X11R6/lib/libGL.so.1
#10 0x0092a992 in _glthread_SetTSD () from /usr/X11R6/lib/libGL.so.1
#11 0x0092ac2e in glXCreateContext () from /usr/X11R6/lib/libGL.so.1
#12 0x554c292e in gdk_gl_context_share_new () from /usr/lib/libgtkgl.so.5
#13 0x554c33f4 in gtk_gl_area_share_new () from /usr/lib/libgtkgl.so.5
#14 0x554c3325 in gtk_gl_area_new () from /usr/lib/libgtkgl.so.5
---Type <return> to continue, or q <return> to quit---
#15 0x5540daef in visual::xglContext::initWindow ()
    from /usr/lib/python2.3/site-packages/cvisualmodule.so
#16 0x553d705f in visual::GLDevice::render_control ()
    from /usr/lib/python2.3/site-packages/cvisualmodule.so
#17 0x553d862f in visual::GLDevice::callback ()
    from /usr/lib/python2.3/site-packages/cvisualmodule.so
#18 0x554da9d5 in g_main_set_poll_func () from /usr/lib/libglib-1.2.so.0
#19 0x554d995b in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#20 0x554d9e47 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#21 0x554da0f5 in g_main_run () from /usr/lib/libglib-1.2.so.0
#22 0x414d753f in gtk_main () from /usr/lib/libgtk-1.2.so.0
#23 0x5540b74d in visual::mainloop ()
    from /usr/lib/python2.3/site-packages/cvisualmodule.so
#24 0x4133498c in start_thread () from /lib/tls/libpthread.so.0
#25 0x410d416a in clone () from /lib/tls/libc.so.6
(gdb)
--

Thanks for looking into this.

Lew

-- 
___________________________________________________
Lew Riley        http://webpages.ursinus.edu/lriley
Ursinus College Department of Physics and Astronomy
(610) 409-3000 ext. 2293       (610) 409-3660 (FAX)

Re: [Visualpython-users] Re: Linux : segmentation faults

[Jonathan B. <jbr...@ea...>]

On Mon, 2004-08-16 at 14:02, Lew Riley wrote:
> Jonathan Brandmeyer wrote:
> 
> > Uh-oh.  Yea, it sounds familiar.  I'm assuming that you have a laptop. 
> > Do you by chance have a Pentium M processor in it (not a Pentium 3-M or
> > Pentium 4-M)?
> 
> Yep. I've got a Dell Latitude D600 with a Pentium M processor.
> 
> > Please run one of the VPython programs that crashes in GDB (the GNU
> > Debugger) by following these instructions, and send me the console
> > output from the entire session.  I'm hoping that setting MESA_DEBUG=1 in
> > the environment will produce something useful, but it might not.
> > 
> 
> OK. Here's the initial output and bactrace from gdb:

Close.  Can you repeat the process, only before you give GDB the "run"
command, give it this one:
`(gdb) handle SIGFPE nostop`
and then complete the process as normal.  The mesa code is supposed to
cause SIGFPE, and then catch it.  Since GDB caught the signal, the catch
wasn't tested (and I think that is where the problem is).  The extra
command above tells GDB not to catch that signal.  It will print out a
message telling you that it was sent, though.

Thanks,
-Jonathan