Launchpad has imported 19 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=448467.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2008-05-27T06:28:17+00:00 Thomas wrote: Description of problem: octave segfaults while executing "clear all". It does not matter if any variables were defined. Version-Release number of selected component (if applicable): octave-3.0.1-1.fc9.x86_64 octave-forge-20080429-1.fc9.x86_64 atlas-3.6.0-15.fc9.x86_64 How reproducible: always Steps to Reproduce: just execute octave --eval "clear all" Actual results: segmentation fault Expected results: no segmentation fault ;) Additional info: (gdb) run -q --eval "clear all" Starting program: /usr/bin/octave -q --eval "clear all" warning: "/usr/lib/debug/usr/lib64/atlas/liblapack.so.3.0.debug": The separate debug info file has no debug info warning: "/usr/lib/debug/usr/lib64/atlas/libblas.so.3.0.debug": The separate debug info file has no debug info [Thread debugging using libthread_db enabled] [New Thread 0x7f8ddaa76700 (LWP 5636)] Program received signal SIGSEGV, Segmentation fault. 0x00000032d95b8496 in symbol_record::clear (this=<value optimized out>) at ov.h:392 392 { return rep->is_defined (); } Current language: auto; currently c++ Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/0 ------------------------------------------------------------------------ On 2008-06-02T08:45:49+00:00 Thomas wrote: The Windows version also segfaults: C:\Programme\Octave>bin\octave -q --eval "clear -all" - Use `pkg list' to see a list of installed packages. - SciTE editor installed. Use `edit' to start the editor. - MSYS shell available (C:\Programme\Octave\msys). - Graphics backend: jhandles. panic: Segmentation violation -- stopping myself... attempting to save variables to `octave-core'... save to `octave-core' complete Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/1 ------------------------------------------------------------------------ On 2008-06-03T09:11:44+00:00 Thomas wrote: It seems that some SWIG-based packages (ann, ftp) are the cause of this problem, so this only happens with octave-forge installed. This is also discussed on octave's mailing list: http://www.cae.wisc.edu/pipermail/bug-octave/2008-May/006094.html Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/2 ------------------------------------------------------------------------ On 2008-09-22T23:46:33+00:00 Oscar wrote: Hi, I followed the suggested link in #2 and ran: > pkg rebuild -noauto ftp database ann at the octave command prompt (octave was run as superuser) and the problem went away.... as far as you don't use ann or the other packages. Hope this helps (and thanks to Thomas) Oscar Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/3 ------------------------------------------------------------------------ On 2008-09-23T03:23:29+00:00 Rakesh wrote: Thanks folks for input - will look into it this weekend. Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/4 ------------------------------------------------------------------------ On 2008-10-23T09:58:06+00:00 Rakesh wrote: Can you folks reproduce for 3.0.2 and give me the input ? Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/5 ------------------------------------------------------------------------ On 2008-10-23T12:39:15+00:00 Thomas wrote: I just tested the packages in rawhide and it still crashes when the octave-forge packages "ftp" or "ann" are loaded. $ rpm -q octave octave-forge octave-3.0.2-1.fc10.x86_64 octave-forge-20080831-2.fc10.x86_64 $ octave -q octave:1> clear all octave:2> pkg load ftp octave:3> clear all panic: Segmentation fault -- stopping myself... attempting to save variables to `octave-core'... save to `octave-core' complete Segmentation fault Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/6 ------------------------------------------------------------------------ On 2008-10-23T13:39:07+00:00 Rakesh wrote: Thanks for input ... I will get back to it soon. Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/7 ------------------------------------------------------------------------ On 2008-12-10T10:02:36+00:00 Alex wrote: I can verify that this is still present in 3.0.3 release. Seems to be an upstream issue in combination with some octave-forge packages perhaps? Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/8 ------------------------------------------------------------------------ On 2009-01-25T22:52:29+00:00 Mark wrote: I confirm that this bugs still occurs with the combination octave-3.0.3-1.fc10.i386 and octave-forge-20080831-2.fc10.i386. Luckily the workaround from #3 still works. Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/9 ------------------------------------------------------------------------ On 2009-03-06T06:32:32+00:00 Rakesh wrote: I did check mailing list and this issue hasn't been been fixed yet. I have asked for status. Waiting for response. Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/12 ------------------------------------------------------------------------ On 2009-03-17T09:04:17+00:00 Rakesh wrote: No response .. this seems to be hanging long! Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/13 ------------------------------------------------------------------------ On 2009-05-17T11:06:19+00:00 Mark wrote: Still in Fedora 11 with Octave 3.0.5 and octave-forge-20080831-8.fc11. Work around still valid. Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/14 ------------------------------------------------------------------------ On 2009-06-10T01:14:02+00:00 Bug wrote: This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/15 ------------------------------------------------------------------------ On 2009-06-11T10:32:27+00:00 Mark wrote: Please update: still present in FC11. Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/16 ------------------------------------------------------------------------ On 2009-08-14T14:31:24+00:00 Alex wrote: *** Bug 517482 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/17 ------------------------------------------------------------------------ On 2009-08-14T14:33:42+00:00 Alex wrote: Can dupe in F-11 when octave-forge is installed and it goes away if octave-forge is removed. The underlying reason does seem to be described in comment #6. These are swig-based packages and reports on the upstream mailing lists suggest that they cause problems. Ideally probably should remove these packages from the octave-forge bundle. Will look into this soon. Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/18 ------------------------------------------------------------------------ On 2009-10-30T08:37:55+00:00 Alex wrote: At least in the case of the "ann" package, I can't reproduce the error with the update in updates-testing (soon to be pushed to F-11 stable): http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10548 octave:1> clear all octave:2> pkg load ann octave:3> clear all octave:4> However, the "ftp" package has been temporarily removed as it failed to build upstream against Octave 3.2.x. Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/19 ------------------------------------------------------------------------ On 2009-11-04T12:25:31+00:00 Fedora wrote: mathgl-1.9-6.fc11.1, plplot-5.9.5-1.fc11, pfstools-1.7.0-8.fc11, GMT-4.5.0-4.fc11, octave-forge-20090607-15.fc11, octave-3.2.3-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/octave2.9/+bug/325118/comments/20 ** Changed in: octave2.9 (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/325118 Title: Octave segfaults on 'clear all' To manage notifications about this bug go to: https://bugs.launchpad.net/octave/+bug/325118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
