[Octave-bug-tracker] [bug #62587] __FILE__ crashes the interpreter

[anônimo]

URL:
  <https://savannah.gnu.org/bugs/?62587>

                 Summary: __FILE__ crashes the interpreter
                 Project: GNU Octave
               Submitter: None
               Submitted: dom 05 jun 2022 20:02:10 UTC
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: Eduardo Pellini
        Originator Email: elpellini@usp.br
             Open/Closed: Open
                 Release: 7.1.0
         Discussion Lock: Any
        Operating System: Microsoft Windows


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: dom 05 jun 2022 20:02:10 UTC   By: Anonymous
Dear friends,

Some (rock solid) scripts i had written in the past started to fail after
upgrade to Octave 7.1.0.

After a lot of 'hide and seek' activities, trying to understand if the problem
was related to some kind of character encoding wars, I found that a single
call (I used it for years) to get the current script location and name, was
crashing the entire interpreter!

It`s easy to reproduce, simply typing...

[ScriptDir, ScriptName, ScriptExt] = fileparts (__FILE__);

... and everything falls apart.

The single call to the keyword __FILE__ in the interpreter is crashing
everything! The GUI exits without any error message.

Running from command prompt I found the following information:

octave:1> __FILE__
panic: impossible state reached in file
'/home/jwe/src/octave-stable/libinterp/parse-tree/oct-parse.yy' at line 2878
fatal: caught signal Aborted -- stopping myself...

My workaround today is to use: 
[ScriptDir, ScriptName, ScriptExt] = fileparts(mfilename('fullpath'));

I'm a brazilian user, using Windows 10 (in portuguese pt-br). I always change
my interface language to 'en_us', and the editor character encoding to 'utf-8'
to avoid problems. I don't guess this is a problem related to these
adjustments.

I guess the problem is somewhat related to some underlying file system
function. Other bug reports describes something wrong with dir() function as
well. I think the problems are related.

I'm available to supply any further information you need.

Keep up the good work!
Eduardo Pellini







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62587>

_______________________________________________
Mensagem enviada pelo Savannah
https://savannah.gnu.org/