cc'ing petter (bytecode interpreter creator)

An octave project using a large DB and complex multi function processing logic and lengthy number crunching (> 20000 Lines Of Code) has been working well with or without the byte-code interpreter active.
By default I use the byte-code interpreter, as it is materially faster.
The code is evolving on a continuous basis and I have experienced no issue with the byte-code interpreter until now.  The octave image is self-build (there is no byte-code image prebuild) from May this year.
The latest byte-code patches not pushed to the byte-code branch are applied manually on top (65240, 64961, 65547, 65304, 65308), some of them needed to be refreshed (like 65304).

A program script execution now causes a core-dump with the byte-code interpreter active (_vm_enable_(1)) and no crash without the byte-code interpreter (_vm_enable_(0)).
The most recent changes are twofold:
i) embedding a function (defined previously via an additional xxxx.m script containing multiple function and executed via source xxxx.m)
ii) calling another function (also previously defined in the same xxxx.m script containing multiple functions as above) which has become a separate stand-alone function file

The program crashes on the line where a simple assignment is coded:

StartC = XXX.STC;

(XXX is a struct)

The trace just before the crash is below.

wSize 6
ans = 38
Trace:
sp  : 0x7ba5897f2ff8
bsp : 0x7ba5897f23e8
sp i: 386
sp ii: 386
ip  : 866
code:
data: 0x7ba5897daa50
ids : 0x7ba5882af700
fn  : ZZZZZZZZZZ
Next op: 1

Trace:
sp  : 0x7ba5897f3000
bsp : 0x7ba5897f23e8
sp i: 387
sp ii: 387
ip  : 868
code:
data: 0x7ba5897daa50
ids : 0x7ba5882af700
fn  : ZZZZZZZZZZ
Next op: 1

Trace:
sp  : 0x7ba5897f2ff8
bsp : 0x7ba5897f23e8
sp i: 386
sp ii: 386
ip  : 869
code:
data: 0x7ba5897daa50
ids : 0x7ba5882af700
fn  : ZZZZZZZZZZ
Next op: 102

ans = 1
Trace:
sp  : 0x7ba5897f2ff0
bsp : 0x7ba5897f23e8
sp i: 385
sp ii: 385
ip  : 873
code:
data: 0x7ba5897daa50
ids : 0x7ba5882af700
fn  : ZZZZZZZZZZ
Next op: 20

Trace:
sp  : 0x7ba5897f2ff8
bsp : 0x7ba5897f23e8
sp i: 386
sp ii: 386
ip  : 875
code:
data: 0x7ba5897daa50
ids : 0x7ba5882af700
fn  : ZZZZZZZZZZ
Next op: 2

Trace:
sp  : 0x7ba5897f3000
bsp : 0x7ba5897f23e8
sp i: 387
sp ii: 387
ip  : 877
code:
data: 0x7ba5897daa50
ids : 0x7ba5882af700
fn  : ZZZZZZZZZZ
Next op: 19

=================================================================================================
Trace:
sp  : 0x7ba5897f2ff8
bsp : 0x7ba5897f23e8
sp i: 386
sp ii: 386
ip  : 880
code:
data: 0x7ba5897daa50
ids : 0x7ba5882af700
fn  : ZZZZZZZZZZ
Next op: 97

Trace:
sp  : 0x7ba5897f2ff0
bsp : 0x7ba5897f23e8
sp i: 385
sp ii: 385
ip  : 882
code:
data: 0x7ba5897daa50
ids : 0x7ba5882af700
fn  : ZZZZZZZZZZ
Next op: 101

Trace:
sp  : 0x7ba5897f2ff8
bsp : 0x7ba5897f23e8
sp i: 386
sp ii: 386
ip  : 884
code:
data: 0x7ba5897daa50
ids : 0x7ba5882af700
fn  : ZZZZZZZZZZ
Next op: 80

Trace:
sp  : 0x7ba5897f2ff8
bsp : 0x7ba5897f23e8
sp i: 386
sp ii: 386
ip  : 890
code:
data: 0x7ba5897daa50
ids : 0x7ba5882af700
fn  : ZZZZZZZZZZ
Next op: 8

Trace:
sp  : 0x7ba5897f2ff0
bsp : 0x7ba5897f23e8
sp i: 385
sp ii: 385
ip  : 892
code:
data: 0x7ba5897daa50
ids : 0x7ba5882af700
fn  : ZZZZZZZZZZ
Next op: 10