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 o


From: Juan Pablo Carbajal
Subject: [Octave-bug-tracker] [bug #44478] test __osmesa_print__.cc-tst crashes on Ubuntu with Nvidia drivers
Date: Fri, 13 Mar 2015 00:27:34 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.89 Safari/537.36

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

Rik,

Thanks for the instructions.
I tried them in my system as well. I still get the segmentation fault

> test __osmesa_print__.cc
panic: Segmentation fault -- stopping myself...
Segmentation fault (core dumped)

I tried the modification in the mercurial repository as well and got the same
result.

I dive into the code and compare it with the demo (see comment #12) that runs
on my computer without a problem. 

There is no need to Enable the GL_*TEST to retrieve the values of
GL_DEPTH_BITS, GL_STENCIL_BITS and GL_ACCUM_RED_BITS. 

And I do not think it is a good idea to disable them before doing the actual
rendering.

I checked that replacing the call to OCTAVE_LOCAL_BUFFER with the code given
in the demo gives the same result.
I also tried to do the retrieval of the values z and s in a local scope, as in
the demo... nothing.

If you comment out all this testing part, then the segmentation fault appears
later.

I guess the segmentation fault has nothing to do with this chuck of code, but
it is something in the configuration of the render that triggers this issue.

We might be barking at the wrong tree.


    _______________________________________________________

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]