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 On Fri, Mar 1, 2019 at 4:36 PM Jason Martin <agrel...@gmail.com> wrote: > 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 > Oorexxfirstname.lastname@example.org > https://lists.sourceforge.net/lists/listinfo/oorexx-devel >
_______________________________________________ Oorexx-devel mailing list Oorexxemail@example.com https://lists.sourceforge.net/lists/listinfo/oorexx-devel