I'm getting a bunch of core files in my ~/hobbit/server directory. Here's an example:
bash-2.05b$ file core.3770 core.3770: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), SVR4-style, from 'hobbitd_larrd'
I wasn't seeing these before I upgraded to RC3.
From hobbitd.log:
2005-02-23 08:12:41 Setup complete 2005-02-23 08:42:57 BOARDBUSY locked at 1, GETNCNT is 0, GETPID is 0, 0 clients 2005-02-23 08:42:57 How did this happen? clients=0, s.sem_op=-1 2005-02-23 08:43:06 Oops ... GOCLIENT is high (1) 2005-02-23 08:43:11 Setup complete 2005-02-23 08:48:19 Setup complete 2005-02-23 10:32:10 Setup complete 2005-02-23 11:37:39 BOARDBUSY locked at 1, GETNCNT is 0, GETPID is 0, 0 clients 2005-02-23 11:37:39 How did this happen? clients=0, s.sem_op=-1 2005-02-23 11:37:49 Oops ... GOCLIENT is high (1) 2005-02-23 11:37:54 Setup complete
Bunch of messages like this in larrd-status.log:
2005-02-23 11:32:32 xfree: Trying to free a NULL pointer2005-02-23 11:32:32 Worker process died with exit code 134, terminating 2005-02-23 11:37:34 xfree: Trying to free a NULL pointer2005-02-23 11:37:34 Worker process died with exit code 134, terminating 2005-02-23 11:42:33 hobbitd_larrd: Got message 1, expected 18932 2005-02-23 11:47:35 xfree: Trying to free a NULL pointer2005-02-23 11:47:35 Worker process died with exit code 134, terminating 2005-02-23 11:52:36 xfree: Trying to free a NULL pointer2005-02-23 11:52:36 Worker process died with exit code 134, terminating 2005-02-23 11:57:37 xfree: Trying to free a NULL pointer2005-02-23 11:57:37 Worker process died with exit code 134, terminating 2005-02-23 12:02:38 xfree: Trying to free a NULL pointer2005-02-23 12:02:38 Worker process died with exit code 134, terminating 2005-02-23 12:07:40 xfree: Trying to free a NULL pointer2005-02-23 12:07:40 Worker process died with exit code 134, terminating
Any ideas?