octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #44478] test __osmesa_print__.cc-tst crashes w


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #44478] test __osmesa_print__.cc-tst crashes with Nvidia drivers
Date: Thu, 12 May 2016 02:09:59 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0

Follow-up Comment #97, bug #44478 (project octave):

In fact, the OpenGL video does act flaky.  Here is the result for John's
second example:


sebald@ ~/octave/opengl_nvidia $ g++ osmesa-fltk-foo-mod.cc -lGL -lOSMesa
-lfltk -lfltk_gl
sebald@ ~/octave/opengl_nvidia $ a.out
GL_DEPTH_BITS: 24
GL_STENCIL_BITS: 0
GL_DEPTH_BITS: 1361941888
GL_STENCIL_BITS: 32766
sebald@ ~/octave/opengl_nvidia $ g++ osmesa-fltk-foo-mod.cc -lOSMesa -lGL
-lfltk -lfltk_gl
sebald@ ~/octave/opengl_nvidia $ a.out
Segmentation fault


In the first case -lGL -lOSMesa, the FLTK X appears in a window and I close
the window and it continues.  In the second case, there's a blip of a window
appearing in the upper left corner, it disappears and Seg-fault appears.

I think there are some inadvertently shared variables and or functions between
nVidia and Mesa.  That, or both started from a similar code base and
programmers didn't bother to change variable/function names.

Any ideas?  All I can think of is to compare the global name's in the two
libraries for what might be common, or compile OSMesa attempting to
iteratively debug where exactly OSMesa is failing in the test programs and
Octave.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44478>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]