This is likely the same trace as the others. Unfortunately, the error is
not in the code that's giving the exception, but caused by something that
happened sometime in the past. The full stack trace might be interesting,
but I suspect it is identical to the other's you've already uploaded.
Rick
Cored on 6; report to github under 20190301
Cored on 14; debugger open to RexxMemory.cpp line 261
I notice and multiple times today (liveMark unable to resolve variable).
Not used to debuggers though.
___
Oorexx-devel mailing list
r11815 up running in test loop on Haiku.
Really cool OS for beta code.
Debugger lets you jump straight to crash and source when you build pkgs.
Just do not know C++ and ooRexx code that well.
___
Oorexx-devel mailing list
On Haiku it cored again on run 25.
I built r11814 for OpenIndiana.
Got to run 22 before it cored.
At run 39, I pushed the machine a little.
Started rexx testOORexx.rex -X native_api in next tab.
Then another.
Then another.
Then another... Froze OS but no cores.
It's stable with just some
