OK I will enable core dumps and wait. Also I'll use monit. It's been running for 43 hours so far; could conceivably do so for days or weeks before it faults again.
In a way it's lucky I experienced the fault so early on: It forced me to confront and be prepared for the possibility. Otherwise, because I go months if not years without seeing Racket fault, it's easy to forget it is even possible. When (if?) I get a core dump for the fault I'll report back. Thanks again to everyone who contributed advice and help. On Sun, Mar 27, 2011 at 9:04 AM, Matthew Flatt <[email protected]> wrote: > At Fri, 25 Mar 2011 19:18:32 -0400, Greg Hendershott wrote: >> I'd posted a week or two ago that Racket was looking for older >> versions of libssl and libcrypto than what the Amazon Linux supplies. >> I'd solved that (I thought?) by making symlinks. Sounds like I should >> revisit that. > > I think that's probably not it. Enabling core dumps is likely the most > useful step for now. > > _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
