abrt 1.0.7 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: octave --eval 'PS1(\'PS1('oc\\PS\'PS1('o\'PS1('oc\\PS1\'PS1('octav\'PS1('octave:\#>');PS2('octave:\#+>'\'P' --persist -H -i comment: I was starting the program from the main menu. component: octave executable: /usr/bin/octave-3.2.3 kernel: 2.6.31.12-174.2.22.fc12.x86_64 package: octave-6:3.2.3-4.fc12 rating: 4 reason: Process /usr/bin/octave-3.2.3 was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine)
Created attachment 396216 [details] File: backtrace
How to reproduce ----- 1.Happens on initial startup 2. 3.
How to reproduce ----- 1. Start QtOctave Comment ----- When starting QtOctave, it starts and crashes. Then, it reloads something... and all is ok (but there's this crash bug and the bug report tool notification).
How to reproduce ----- 1.Happens on initial startup of QtOctave 2. 3. Comment ----- >>>warning: mark_as_command is obsolete and will be removed from a future versi on of Octave >>>panic: Segmentation fault -- stopping myself... attempting to save variables to `octave-core'... save to `octave-core' complete This is the error message received. I noticed that the >>> appeared before the warning before the crash. When the warning appears normally the >>> does not appear before the warning, ie. warning: mark_as_command is obsolete and will be removed from a future version of Octave
How to reproduce ----- 1.save a large file of variables in QtOctave: ie. save largefile.mat; 2.shutdown and restart QtOctave 3.attempt to load largefile.mat ie: load largefile.mat; Comment ----- This seems to cause the same segmentation fault that occasionally occurs on startup. Since the Octave startup includes reloading the last set of variables in use it seems likely that this is related, if not the same problem. I examined the data file that caused the crash, a number of the variables had changed, possibly due to rounding error, to become much higher precision. Possibly some type of register overflow might occur. This saved file also crashes vanilla Octave if you attempt to load it, with the same segmentation fault.
(In reply to comment #5) > > How to reproduce > ----- > 1.save a large file of variables in QtOctave: ie. save largefile.mat; > 2.shutdown and restart QtOctave > 3.attempt to load largefile.mat ie: load largefile.mat; Can you reproduce with vanilla command-line octave? If not, then this is most likely qtoctave-specific and probably need to switch the Bugzilla component and/or discuss with upstream qtoctave.
Comment ----- Exited QtOctave. This seems to generate an Octave Crash.
Hi, This bug is still there in the new version of qtoctave (qtoctave-0.9.1.1.fc12.x86_64). Any proposed fix? Thanks, Enrique
This is almost certainly a dupe of bug #562276 and the problem is with octave-forge, not qtoctave per se. *** This bug has been marked as a duplicate of bug 562276 ***