[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: Guillaume
Subject: [Octave-bug-tracker] [bug #57529] Crash with qhull v7.3.2 (2019.1)
Date: Tue, 7 Jan 2020 05:01:58 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

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

@Kai: Thanks for looking into this. I am indeed using the
"science"-repository. Following your suggestion, I started again a clean build
and was expecting to confirm your findings but I still reproduce the issue
100% of the time.

octave:1> x = -3:0.05:3; y = abs (sin (x)); k = convhull (x, y);
error: =: nonconformant arguments (op1 is 1x1, op2 is 358x1)
error: called from
    convhull at line 158 column 14
octave:2> x = rand (10, 1); y = rand (10, 1); tri = delaunay (x, y); [vx, vy]
= voronoi (x, y, tri);
fatal: caught signal Segmentation fault -- stopping myself...
Segmentation fault (core dumped)

I am still not ruling out a specific issue on my machine(s) but I will try to
run the debugger and get a stacktrace as suggested by Rik.

Information for package qhull:
Repository     : science                                                      
Name           : qhull                                                        
Version        : 2019.1-lp150.6.1                                             
Arch           : x86_64                                                       
Vendor         : obs://build.opensuse.org/science                             
Installed Size : 3.5 MiB                                                      
Installed      : Yes                                                          
Status         : up-to-date                                                   
Source package : qhull-2019.1-lp150.6.1.src                                   
Summary        : Computing convex hulls, Delaunay triangulations and Voronoi


Reply to this item at:


  Message sent via Savannah

reply via email to

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