Bill, It's a segmentation fault.
It was probably caused by a memory error. There's not enough information there to know for sure. Robert -----Original Message----- From: William Conlon [mailto:[email protected]] Sent: Sunday, July 10, 2011 12:50 PM To: [email protected] Subject: Witango-Talk: First ever witangod5 linux crash since 2003 [ 2432] 2011-07-07 02:10:36 RUNTIME FATAL Caught fatal signal 11 (SIGSEGV); thread id = -1502004304; code: 1; address: 00000019; value: 00e5389c; errno: 0; status: 15022236; Running Fedora Core 4 witango 5.0.1.065 server is otherwise fine as far as I can tell. I restarted witangod and everything appears fine. But I'm curious if anyone knows what this signal indicates? Thx. Bill ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body.
