[Top][All Lists]

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

[Octave-bug-tracker] [bug #57529] Crash with qhull v7.3.2 (2019.1)

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #57529] Crash with qhull v7.3.2 (2019.1)
Date: Tue, 7 Jan 2020 11:28:43 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Follow-up Comment #16, bug #57529 (project octave):

I built a copy of qhull 2019.1 from source and initially had some strange
crashes.  When I looked at the data in gdb it looked fine, but then would
crash with segfaults while looping over vertices.

Then I noticed that the layouts of some internal structures like the global
qh_qh object that we use (struct qhT in libqhull.h) have changed and I was
trying to just use the new libqhull.so that I built as a drop-in replacement
with my already built copy of Octave that was compiled with an older version
of Qhull.  But that won't work because the structure layouts have changed.  So
you must rebuild and execute with a consistent set of Qhull libraries and
header files.  Once I did that, it seems to work properly again.

The functions that use Qhull are .oct files, so those must be rebuilt and
linked with the correct and consistent version of Qhull headers and

Of course there may be other issues, but I'm currently unable to duplicate the

If you can build Qhull with debugging symbols can you also try without the
address sanitizer and instead just use gdb and get a stack trace at the point
of the segfault?

I build Qhull with debugging symbols using

cd qhull-2019.1/build
cmake -DCMAKE_INSTALL_PREFIX=/home/jwe/build/qhull -DCMAKE_BUILD_TYPE=Debug
make install

and then built and executed Octave with

LD_LIBRARY_PATH=/home/jwe/build/qhull/lib /path/to/configure ...

LD_LIBRARY_PATH=/home/jwe/build/qhull/lib ./run-octave 


Reply to this item at:


  Message sent via Savannah

reply via email to

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