Re: [osg-users] setMaxAnisotropy() Causes Segfault

2021-02-18 Thread merspieler
On Thu, Feb 18, 2021 at 05:08:36PM +, Robert Osfield wrote: > The texture->setMaxAnisotropy() is a straight forward C++ method, the only > reason for it to crash would be for the method to be called on a nullptr or > invalid texture pointer. Thanks for the hint. I've checked that with gdb,

Re: [osg-users] setMaxAnisotropy() Causes Segfault

2021-02-18 Thread Robert Osfield
The texture->setMaxAnisotropy() is a straight forward C++ method, the only reason for it to crash would be for the method to be called on a nullptr or invalid texture pointer. Most likely the bug stems from simgear so I would suggest contacting the FlightGear team to see if they can reproduce the

[osg-users] setMaxAnisotropy() Causes Segfault

2021-02-18 Thread merspieler
I was told to ask here for help on this. I'm receiving a SIGSEGV when texture->setMaxAnisotropy() is called. According to the header file texture is: osg::ref_ptr texture; I'm not familiar with osg nor the code that causes it so I hope, you can help me. Thread 1 "fgfs" received signal SIGSEGV,