Bug 629414 - [abrt] octave-6:3.2.4-2.fc13: raise: Process /usr/bin/octave-3.2.4 was killed by signal 6 (SIGABRT)
Summary: [abrt] octave-6:3.2.4-2.fc13: raise: Process /usr/bin/octave-3.2.4 was killed...
Keywords:
Status: CLOSED DUPLICATE of bug 618450
Alias: None
Product: Fedora
Classification: Fedora
Component: octave
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Rakesh Pandit
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:aff5da62414e35625718d90ed77...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-01 22:35 UTC by Sang Tae Park
Modified: 2010-12-29 08:37 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-29 08:37:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (20.73 KB, text/plain)
2010-09-01 22:35 UTC, Sang Tae Park
no flags Details

Description Sang Tae Park 2010-09-01 22:35:12 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: octave
component: octave
crash_function: raise
executable: /usr/bin/octave-3.2.4
kernel: 2.6.34.6-47.fc13.x86_64
package: octave-6:3.2.4-2.fc13
rating: 4
reason: Process /usr/bin/octave-3.2.4 was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1283380383
uid: 501

How to reproduce
-----
1.octave
2.bessel_Jn(1,1)
3.

Comment 1 Sang Tae Park 2010-09-01 22:35:14 UTC
Created an attachment (id=442508)
File: backtrace

Comment 2 Sang Tae Park 2010-09-02 15:02:14 UTC
Package: octave-6:3.2.4-2.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.octave
2.legendre_Plm(1,1,0)
3.

Comment 3 Susi Lehtola 2010-09-02 15:16:41 UTC
I can reproduce this as well.

gdb output:
octave:1> legendre_Plm(1,1,0)
*** glibc detected *** /usr/bin/octave: free(): invalid pointer: 0x00007fcf4d3b0f30 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3843475676]
/usr/lib64/octave-3.2.4/liboctinterp.so(_ZN21tree_index_expression7rvalue1Ei+0x9e)[0x7fcf4cbb5b7e]
/usr/lib64/octave-3.2.4/liboctinterp.so(_ZN14tree_evaluator15visit_statementER14tree_statement+0x106)[0x7fcf4cba9636]
/usr/lib64/octave-3.2.4/liboctinterp.so(_ZN14tree_evaluator20visit_statement_listER19tree_statement_list+0x58)[0x7fcf4cba6658]
/usr/lib64/octave-3.2.4/liboctinterp.so(_Z9main_loopv+0x14e)[0x7fcf4c9dabce]
/usr/lib64/octave-3.2.4/liboctinterp.so(octave_main+0xf37)[0x7fcf4c970367]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x384341ec5d]
/usr/bin/octave[0x4007f9]

valgrind output:
octave:1> legendre_Plm(1,1,0)
==21770== Invalid free() / delete / delete[]
==21770==    at 0x4A04A84: operator delete(void*) (vg_replace_malloc.c:346)
==21770==    by 0x5306B7D: tree_index_expression::rvalue1(int) (ov.h:328)
==21770==    by 0x52FA635: tree_evaluator::visit_statement(tree_statement&) (pt-eval.cc:699)
==21770==    by 0x52F7657: tree_evaluator::visit_statement_list(tree_statement_list&) (pt-eval.cc:735)
==21770==    by 0x512BBCD: main_loop() (toplev.cc:574)
==21770==    by 0x50C1366: octave_main (octave.cc:885)
==21770==    by 0x384341EC5C: (below main) (libc-start.c:226)
==21770==  Address 0x5b01f30 is in the BSS segment of /usr/lib64/octave-3.2.4/liboctinterp.so.3.2.4
==21770== 
ans = -1


And there seems to be a misprint in the help page:

 -- Loadable Function: Y = legendre_Plm (N, M, X)
 -- Loadable Function: [Y, ERR] = legendre_Plm (...)
     These routines compute the associated Legendre polynomial P_l^m(x)
     for m >= 0, l >= m, |x| <= 1.

N should probably read L.

Comment 4 Thomas Sailer 2010-09-07 10:54:48 UTC
Package: octave-6:3.2.4-2.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.octave
2.gf(0)


Comment
-----
Any of the galois field related functions seem to crash, such as primpoly
Same for fc14, but works on fc12.

Comment 5 lchacon1 2010-09-09 14:35:35 UTC
Package: octave-6:3.2.4-2.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Start 64-bit version of octave
2. Execute "bessel_zero_J0(1)"
3.


Comment
-----
This function belongs to the GSL library. The function "bessel_zero_J0" works in 32-bit version.

Comment 6 el erit 2010-10-27 13:18:56 UTC
Package: octave-6:3.2.4-2.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.Octave
2. waitbar function
3. crash


Comment
-----
waitbar function on octave crash

Comment 7 el erit 2010-10-28 16:10:35 UTC
Package: octave-6:3.2.4-2.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. octave
2. for cycle
3. then waitbar crash


Comment
-----
waitbar function octave crash

Comment 8 ccancellieri 2010-11-02 17:36:29 UTC
Package: octave-6:3.2.4-2.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. running octave
2. calling 'netcdf'

Comment 9 ccancellieri 2010-11-03 16:34:01 UTC
(In reply to comment #8)
> Package: octave-6:3.2.4-2.fc13
> Architecture: i686
> OS Release: Fedora release 13 (Goddard)
> 
> 
> How to reproduce
> -----
> 1. running octave
> 2. calling 'netcdf'

do not happen using octave-forge-20090607-15.fc12.i686

Comment 10 ccancellieri 2010-11-03 18:51:33 UTC
(In reply to comment #8)
> Package: octave-6:3.2.4-2.fc13
> Architecture: i686
> OS Release: Fedora release 13 (Goddard)
> 
> 
> How to reproduce
> -----
> 1. running octave
> 2. calling 'netcdf'

do not happen using octave-forge-20090607-15.fc12.i686

Comment 11 Bert van Ulft 2010-12-02 09:08:42 UTC
(In reply to comment #10)
> (In reply to comment #8)
> > Package: octave-6:3.2.4-2.fc13
> > Architecture: i686
> > OS Release: Fedora release 13 (Goddard)
> > 
> > 
> > How to reproduce
> > -----
> > 1. running octave
> > 2. calling 'netcdf'
> 
> do not happen using octave-forge-20090607-15.fc12.i686

I have the same problem.
On Fedora 13, octave 3.2.4 with octave-forge-20090607-17.fc13.i686 crashes when trying to read a netcdf file (nc = netcdf('test.nc,'r');).
Doing the same thing with octave-forge-20090607-15.fc12.i686 works fine.

Comment 12 Rakesh Pandit 2010-12-29 08:37:49 UTC

*** This bug has been marked as a duplicate of bug 618450 ***


Note You need to log in before you can comment on or make changes to this bug.