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: Rik
Subject: [Octave-bug-tracker] [bug #44478] test __osmesa_print__.cc-tst crashes on Ubuntu with Nvidia drivers
Date: Wed, 08 Apr 2015 23:10:39 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0

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

@Andreas: Does ordinary plotting in core Octave work with the NVidia drivers?

I notice, obviously, that both __osmesa_print__.cc and your simple example are
dynamically loaded.  Maybe there are compile/linker flags that we are not
setting correctly?

The first two items of Nvidia's known problems list are


OpenGL and dlopen()

    There are some issues with older versions of the glibc dynamic loader
(e.g., the version that shipped with Red Hat Linux 7.2) and applications such
as Quake3 and Radiant, that use dlopen(). See Chapter 7, Frequently Asked
Questions for more details.

Interaction with pthreads

    Single-threaded applications that use dlopen() to load NVIDIA's libGL
library, and then use dlopen() to load any other library that is linked
against libpthread will crash in libGL. This does not happen in NVIDIA's new
ELF TLS OpenGL libraries (see Chapter 5, Listing of Installed Components for a
description of the ELF TLS OpenGL libraries). Possible workarounds for this
problem are:

      1)  Load the library that is linked with libpthread before loading
libGL.

      2)  Link the application with libpthread.


I can't say whether your system has an old glibc.  But for pthreads,
everything seems okay.  When I do 'make clean; make V=1' I see that the lines
for core Octave have -pthread and so do the dynamically loaded modules in the
dldfcn/ directory.

Maybe, there is a problem with the fact that octave is itself just a small
executable that exec's itself out of the way.  Instead of ./run-octave you
could do 'make install' and then try directly running octave-cli-4.0.0-rc2 and
your test program.


    _______________________________________________________

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]