core on 18 and 19 reports at github.
Both:
state: Exception (Segment violation)
Frame IP Function Name
---
0x7f954dae3ce0 0x9b13ee
MemoryObject::mar
r11814 builds, crash on run 12.
Did not even look at report, will leave running.
Look at next one.
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Segfaults under OpenIndiana and Haiku running rexx rexxcps.rex
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Unfortunately the fix breaks more things than it fixes
[enrico@enrico-imac ooRexx.svn.testSuite]$lldb -- rexx testOORexx.rex -s -X
native_API -x FUNCTION.testGroup
(lldb) target create "rexx"
Current executable set to 'rexx' (x86_64).
(lldb) settings set -- target.run-args "testOORexx.rex" "-s
I just committed a fix that I think closes a GC problem window. Not
terribly confident this is a fix for the crash you were seeing, but the
stack traces you provided at least hint that it might be.
Rick
On Thu, Feb 28, 2019 at 7:54 AM Jason Martin wrote:
> Stopping on run 100 using r11811.
>
>
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 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/
