[Octave-bug-tracker] [bug #64574] VM causes "'%nargout' undefined near line" error

[anonymous]

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

                 Summary: VM causes "'%nargout' undefined near line" error
                   Group: GNU Octave
               Submitter: None
               Submitted: Sun 20 Aug 2023 08:23:05 AM UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error or Warning
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: GNU/Linux
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Sun 20 Aug 2023 08:23:05 AM UTC By: Anonymous
The VM causes an error "'%nargout' undefined near line".

This is always reproducible as part of my rather large DB and octave program
which is not shareable. 
Unfortunately I did not manage to recreate this error within a small test
program using a few variables (I tried not too hard though). 

But the error and the error message seems revealing. It occurs in the first
iteration of a loop containing complex business logic.
The program line which fails with the error message is

c = round(mean(a - b) + 0.2);

Interesting enough: If I split the command into separate statements, the
program works fine with VM enabled( __enable_vm_eval__ (1)) without error:

a1 = mean(a - b) + 0.2;
c = round(a1 + 0.2);

Additional information
======================
If I catch the error in debug mode and execute the command manually (so via
octave interpreter), it works without error. 

a and b are a 12x1 vector in this first iteration with the same values, so the
overall result is 0
mean(a-b) = 0 and round(0+0.2) = 0

Of course the program works overall fine with  __enable_vm_eval__ (0)








    _______________________________________________________

Reply to this item at:

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

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/