In an operating system I worked with as a system administrator, an out-of-memory condition caused a similar failure-without-notice, which the vendor fixed by allocating a memory page at start-up reserved solely for space for producing appropriate failure messages.
Leslie On 2018-08-26 12:00:50 Rick McGuire wrote: > Yes, I understand, but the root cause of this problem is a failure trying > to expand the liveStack during a garbage collection. The call to > reportException() at that time causes a recursive allocation failure, > resulting in the eventual out-of-stack condition. I suspect the only real > way to handle this situation is a calling logicError() to indicate there > has been an unrecoverable out of memory situation. > > Rick > > On Sun, Aug 26, 2018 at 12:56 PM Erich Steinböck > <erich.steinbo...@gmail.com> > > wrote: > > The actual failure is stack overflow (due the the infinite recursion it > > goes into) > > > > Unhandled exception at 0x000007FED88162FC (rexx.dll) in rexx.exe: > > 0xC00000FD: Stack overflow (parameters: 0x0000000000000001, > > 0x00000000000D3FC0). > > > > ------------------------------------------------------------------------- > >----- Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Oorexx-devel mailing list > > Oorexx-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
