[Glass] GS Fatal Internal Error, 5015, 15621, IO Error (RepRead Error)

Bill Erickson bill.erickson at gemtalksystems.com
Mon Jul 28 09:45:21 PDT 2014

Setting GEM_HALT_ON_ERROR in the session's config file to the number of the
error you want more diagnostic data on will cause a stack trace to be
printed out to the gem log.  That would be a start...

Bill Erickson
GemTalk Systems Engineering
15220 NW Greenbrier Parkway #240, Beaverton OR 97006

On Mon, Jul 28, 2014 at 2:28 AM, <pieter at nagel.co.za> wrote:

> It really seems this bug only occurs when tranlogging to /dev/null.
> It's now two weeks later after switching tranlogs to real directories, and
> this bug still has not resurfaced. Used to happen a handful of times a
> week.
> But on development test-suites etc. run about 3 times faster when
> tranlogging to /dev/null.
> Is there other way to get debug information on this while still
> tranlogging to /dev/null?
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20140728/ef5dd63d/attachment.html>

More information about the Glass mailing list