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

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

[Octave-bug-tracker] [bug #48669] Segfaults at exit after using OpenGL-b


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #48669] Segfaults at exit after using OpenGL-based toolkits in --no-gui mode
Date: Tue, 2 Aug 2016 05:22:28 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0

Follow-up Comment #5, bug #48669 (project octave):

No difference; exact same output and crashes.  Here are some entries from my
config.log:


configure:19791: WARNING: --without-OSMesa specified.  Functions or features
that depend on OSMesa will be disabled.

octave_cv_lib_OSMesa=no

config_opts=' '\''--without-OSMesa'\'''


I also checked the date of $builddir/src/octave to make sure it was built
after the configuration.

You're thinking that this is that OSMesa/Nvidia issue?

https://savannah.gnu.org/bugs/?func=detailitem&item_id=44478

I'd forgotten about that, but wasn't that related to printing, not rendering? 
Something like OSMesa isn't technically following OpenGL, just makes it seem
so?  Or is there something similar regarding Gallium/Nouveau?  Although I
wouldn't think so, because that would defeat the purpose of OpenGL
standardization.

I'll hunt around a bit for what routine exactly is failing for FLTK.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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