[Octave-bug-tracker] [bug #37076] Running octave on a mounted windows cifs share crashes

[anonymous]

URL:
  <http://savannah.gnu.org/bugs/?37076>

                 Summary: Running octave on a mounted windows cifs share
crashes
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Sa 11 Aug 2012 17:28:33 UTC
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Crash
                  Status: None
             Assigned to: None
         Originator Name: T. Finke
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.2.4
        Operating System: GNU/Linux

    _______________________________________________________

Details:

Bug report for Octave 3.2.4 configured for i686-pc-linux-gnu

Description:
-----------

(This description reports a problem on an older version of octave. Newer
versions seem to work without any problem. But it may be useful for people
that cannot upgrade to a recent   version for any reason)

Running octave on a mounted windows cifs share crashes.
  
Already at startup octave shows it's entry message and then  immediately
panics with the message: 

      
      GNU Octave, version 3.2.4
      Copyright (C) 2009 John W. Eaton and others.
      ...      
      panic: impossible state reached in file `load-path.cc' at line 657
      panic: Aborted -- stopping myself...
      attempting to save variables to `octave-core'...
      save to `octave-core' complete

The message "panic: impossible state reached in file `load-path.cc'" can be
found according to several problems concerning package management. 

Repeat-By:
---------

- mount a cifs share from a windows(!) system
- cd to the mount point
- run octave -> crashes immediately

Interestingly this does happen only on shares from windows systems, not on a
cifs share from a samba server.
  

Fix:
---

none found yet. Only a workaround: copy data to a local file system and run
octave there; afterwards copy results back. 








    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?37076>

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/