Segfault on dot(v,v')

Bug #1849460 reported by George Kontsevich
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
octave (Ubuntu)
New
Undecided
Unassigned

Bug Description

Octave was installed with apt-get install octave on a normal x64 machine running Ubuntu 19.04 disco
No funny stuff. And all Recommended and Suggested packages were installed
I get a segfault on the simple input:

v = [3+4i 6+8i]
dot(v,v')

This is in GUI, CLI, octave-cli and running with sudo. Crashes in all cases with:

fatal: caught signal Segmentation fault -- stopping myself...
Segmentation fault

PS:
I've also separately test the Octave Snap package and it doesn't have this issue (but it doesn't run correctly with Emacs/Orgmode so it's not useful for me)

Revision history for this message
George Kontsevich (geokon) wrote :
Download full text (3.3 KiB)

Running through gdb, crashing, and then printing the backtrace:
_________________________________________________________________________

Starting program: /usr/bin/octave-cli
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe7bd5700 (LWP 7971)]
GNU Octave, version 4.4.1
Copyright (C) 2018 John W. Eaton and others.
This is free software; see the source code for copying conditions.
There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. For details, type 'warranty'.

Octave was configured for "x86_64-pc-linux-gnu".

Additional information about Octave is available at https://www.octave.org.

Please contribute if you find this software useful.
For more information, visit https://www.octave.org/get-involved.html

Read https://www.octave.org/bugs.html to learn how to submit bug reports.
For information about changes from previous versions, type 'news'.

octave:1> v = [3+4i 6+8i]
v =

   3 + 4i 6 + 8i

octave:2> dot(v,v')

Thread 1 "octave-cli" received signal SIGSEGV, Segmentation fault.
0x00007ffff725897f in octave_value::operator=(octave_value const&) () from /lib/x86_64-linux-gnu/liboctinterp.so.6
(gdb) bt
#0 0x00007ffff725897f in octave_value::operator=(octave_value const&) () from /lib/x86_64-linux-gnu/liboctinterp.so.6
#1 0x00007ffff78ea45d in Fdot(octave_value_list const&, int) () from /lib/x86_64-linux-gnu/liboctinterp.so.6
#2 0x00007ffff7622828 in octave_builtin::call(octave::tree_evaluator&, int, octave_value_list const&) () from /lib/x86_64-linux-gnu/liboctinterp.so.6
#3 0x00007ffff77c12dc in octave::tree_evaluator::visit_index_expression(octave::tree_index_expression&) () from /lib/x86_64-linux-gnu/liboctinterp.so.6
#4 0x00007ffff7664e9e in octave::tree_evaluator::evaluate(octave::tree_expression*, int) () from /lib/x86_64-linux-gnu/liboctinterp.so.6
#5 0x00007ffff77bd2cf in octave::tree_evaluator::visit_statement(octave::tree_statement&) () from /lib/x86_64-linux-gnu/liboctinterp.so.6
#6 0x00007ffff77b5b80 in octave::tree_evaluator::visit_statement_list(octave::tree_statement_list&) () from /lib/x86_64-linux-gnu/liboctinterp.so.6
#7 0x00007ffff7aa47d6 in octave::interpreter::main_loop() () from /lib/x86_64-linux-gnu/liboctinterp.so.6
#8 0x00007ffff7aaa5ad in octave::interpreter::execute() () from /lib/x86_64-linux-gnu/liboctinterp.so.6
#9 0x00007ffff722db57 in octave::cli_application::execute() () from /lib/x86_64-linux-gnu/liboctinterp.so.6
#10 0x000055555555534c in ?? ()
#11 0x00007ffff5a30b6b in __libc_start_main (main=0x555555555200, argc=1, argv=0x7fffffffde18, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffde08) at ../csu/libc-start.c:308
#12 0x000055555555556a in ?? ()
(gdb)

_________________________________________________________________________

Just to sanity check, this lib is where it's supposed to be:

geokon@ux305-ubuntu:~$ ll /lib/x86_64-linux-gnu/liboctinterp.so*
lrwxrwxrwx 1 root root 21 3月 1 2019 /lib/x86_64-linux-gnu/liboctinterp.so -> liboctinterp.so.6.0.0
lrwxrwxrwx 1 root root 21 3月 1 2019 /lib/x86_64-...

Read more...

Revision history for this message
George Kontsevich (geokon) wrote :

I also upgraded to Ubuntu 19.10 eoan and the problem is still there

Revision history for this message
George Kontsevich (geokon) wrote :

This issue doesn't exist on 18.04 LTS and hence I've downgraded. Hope this is resolved before the next LTS release in the spring

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.