[Octave-bug-tracker] [bug #64749] VM seems to be out of sync in very rare situations for function parameters

[anonymous]

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

                 Summary: VM seems to be out of sync in very rare situations
for function parameters
                   Group: GNU Octave
               Submitter: None
               Submitted: Thu 05 Oct 2023 03:35:24 PM UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  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: Thu 05 Oct 2023 03:35:24 PM UTC By: Anonymous
The VM seems to be out of sync in very rare situations. Within a very long
function, all of a sudden one of the function parameters (one containing a
struct) is overwritten / initialised to be empty.
(Without the VM everything works fine.)



r is the function parameter containing a struct variable.


   # disp(r)
   disp(NrPast);
   for jj=1:NrPast
     ...
   endfor
   if isempty(r)
      error("Function parameter is empty");
    endif


Note : NrPast is Zero so the loop is not executed.

-->
0
error: Function parameter is empty
error: called from
    fname at line 1966 column 7
    @<anonymous>
 
If I just remove the commented out disp(r) and make it executed, then r is
displayed (and has its original content), r is not empty and the isempty error
check is not thrown, but an error due to r being empty is thrown much further
down the same function.


   disp(r)
   disp(NrPast);
   for jj=1:NrPast
     ...
   endfor
   if isempty(r)
      error("Function parameter is empty");
    endif

-->

error: matrix cannot be indexed with .
error: called from
    fname at line 3695 column 24
    @<anonymous>

---------------------------------------------------------------
Trace-log is below of the last few statements in the second case

Trace:
sp  : 0x7f92901b1078
bsp : 0x7f92901af1e0
sp i: 979
sp ii: 1016
ip  : 61918
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 20

Trace:
sp  : 0x7f92901b1080
bsp : 0x7f92901af1e0
sp i: 980
sp ii: 1017
ip  : 61920
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 20

Trace:
sp  : 0x7f92901b1088
bsp : 0x7f92901af1e0
sp i: 981
sp ii: 1018
ip  : 61922
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 140

Trace:
sp  : 0x7f92901b1090
bsp : 0x7f92901af1e0
sp i: 982
sp ii: 1019
ip  : 61926
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 103

Trace:
sp  : 0x7f92901b1098
bsp : 0x7f92901af1e0
sp i: 983
sp ii: 1020
ip  : 61928
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 82

Trace:
sp  : 0x7f92901b1098
bsp : 0x7f92901af1e0
sp i: 983
sp ii: 1020
ip  : 61934
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 42

Trace:
sp  : 0x7f92901b1088
bsp : 0x7f92901af1e0
sp i: 981
sp ii: 1018
ip  : 61937
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 42

Trace:
sp  : 0x7f92901b1080
bsp : 0x7f92901af1e0
sp i: 980
sp ii: 1017
ip  : 61940
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 41

Trace:
sp  : 0x7f92901b1088
bsp : 0x7f92901af1e0
sp i: 981
sp ii: 1018
ip  : 61942
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 140

Trace:
sp  : 0x7f92901b1078
bsp : 0x7f92901af1e0
sp i: 979
sp ii: 1016
ip  : 61947
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 140

Trace:
sp  : 0x7f92901b1080
bsp : 0x7f92901af1e0
sp i: 980
sp ii: 1017
ip  : 61951
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 103

Trace:
sp  : 0x7f92901b1088
bsp : 0x7f92901af1e0
sp i: 981
sp ii: 1018
ip  : 61953
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 140

Trace:
sp  : 0x7f92901b1090
bsp : 0x7f92901af1e0
sp i: 982
sp ii: 1019
ip  : 61957
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 20

Trace:
sp  : 0x7f92901b1098
bsp : 0x7f92901af1e0
sp i: 983
sp ii: 1020
ip  : 61959
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 140

Trace:
sp  : 0x7f92901b10a0
bsp : 0x7f92901af1e0
sp i: 984
sp ii: 1021
ip  : 61963
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 42

Trace:
sp  : 0x7f92901b1098
bsp : 0x7f92901af1e0
sp i: 983
sp ii: 1020
ip  : 61966
code: 0x7f92b773aec0
data: 0x7f921fabf7f0
ids : 0x7f921fec6860
fn  : fname
Next op: 96

 







    _______________________________________________________

Reply to this item at:

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

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