Both crashes point to a garbage collection problem, which can be notoriously difficult to debug. The tracebacks show that the crashes are occurring doing the same activity, which might give a starting point for finding the failure point.
Rick On Thu, Feb 28, 2019 at 7:54 AM Jason Martin <agrel...@gmail.com> wrote: > Stopping on run 100 using r11811. > > I have exceeded the limits of my medication... > > Summary of all completed runs (over 30,000 total testGroups): > ~> grep -e Failures: -e Errors: full_run.log | sort | uniq -c > 94 Errors: 0 > 94 Failures: 0 > > At https://github.com/agrellum/NetRexx-Samples > > Crash on runs 9 and 72 saved report > rexx-826-debug-27-02-2019-19-20-56.report > rexx-9516-debug-28-02-2019-03-57-52.report > > Crash on runs 86, 89, 95 and 96 saved core file > core-rexx-12579 core-rexx-15982 core-rexx-16223 core-rexx-16238 > > OK, must have been in the fine print. > > remote: error: File core-rexx-12579 is 175.33 MB; > this exceeds GitHub's file size limit of 100.00 MB > > So it's compress one potato, two potato ... > > There are pre-built packages with debug symbols. > oorexx-5.0.0-1-x86_64.hpkg > oorexx_source-5.0.0-1-source.hpkg > Just copy them to /boot/system/packages > > There is archive of patchset and recipe used to build in Haikuports. > oorexx.tar.gz > > There is archive of my patched test suite with > clean.sh, count.sh and singles.sh. > test.tar.gz > > If anybody wants to do Virtualbox and debug, get same image as me. > > > https://cdn.haiku-os.org/haiku-nightly/x86_64/haiku-master-hrev52939-x86_64-anyboot.zip > > You have gdb and nice graphical debugger listed in the Applications Menu > > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
