Bug#917959: octave: segfault on complex dot product

2019-01-02 Thread Bernhard Übelacker
Hello Adam Knapp, you might run octave inside gdb to retrieve a backtrace of the crash. Run below command inside a terminal application and you should receive a file gdb-octave*.log that you might forward to this bug. gdb -q -batch -ex 'set pagination off' -ex 'set width 0' -ex run -ex 'bt ful

Bug#917959: octave: segfault on complex dot product

2019-01-02 Thread Sébastien Villemot
Dear Adam, Le mardi 01 janvier 2019 à 11:17 -0500, Adam Knapp a écrit : > Package: octave > Version: 4.4.1-2+b1 > Severity: important > Below, we have what I tried: > > octave:1> dot([i i], [i i]) > fatal: caught signal Segmentation fault -- stopping myself... > Segmentation fault > > > This s

Bug#917959: octave: segfault on complex dot product

2019-01-01 Thread Rafael Laboissière
Control: tags -1 unreproducible moreinfo Control: severity -1 normal * Adam Knapp [2019-01-01 11:17]: Package: octave Version: 4.4.1-2+b1 Severity: important Below, we have what I tried: octave:1> dot([i i], [i i]) fatal: caught signal Segmentation fault -- stopping myself... Segmentation

Bug#917959: octave: segfault on complex dot product

2019-01-01 Thread Adam Knapp
Package: octave Version: 4.4.1-2+b1 Severity: important Hello, Below, we have what I tried: octave:1> dot([i i], [i i]) fatal: caught signal Segmentation fault -- stopping myself... Segmentation fault This should return 2, just like the real number version (and like Matlab). Other variations