search for: num_share_mode_entries

...roblem is not reproducable, but only happens from time to time (say every few hours). I've had a look at the samba logs for his pc and this is what happens at the time that he has the error. [1999/01/27 16:32:07, 0] locking/locking_shm.c:shm_set_share_mode(486) PANIC ERROR:set_share_mode num_share_mode_entries=-12 [1999/01/27 16:32:07, 2] locking/locking_shm.c:shm_del_share_mode(354) del_share_modes Deleting share mode entry dev=800047 ino=464779 [1999/01/27 16:32:07, 0] locking/locking_shm.c:shm_del_share_mode(367) PANIC ERROR:del_share_mode num_share_mode_entries=-13 Here's some more errors...

...ccuring where I noted below. I now have data values to go along with the location. The SIGBUS generating bit is "entry_scanner_p->e.pid" which looks to be in an unaccessable area of memory. Looking back through the code, I find a couple of bizarities. For example file_scanner_p->num_share_mode_entries comes back as 1651272501, which, if I understand the code, is a bit large. It looks as if the code is accessing memory it's not supposed to be accessing. Well, it looks like a memory error. I'd been meaning to try out the new version of Purify anyway, so I guess I'll go ahead and dow...