Displaying 2 results from an estimated 2 matches for "file_scanner_p".
2000 Jun 12
0
smbstatus getting a SIGBUS error
...e sigbus error is occuring 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 gues...
2000 Jan 11
0
SAMBA BUG: smbstatus 2.0.6 core dumps on Solaris 2.6 (SIGSEGV)
...t locking/locking_shm.c:636
#1 0x1c668 in share_mode_forall (fn=0x1b3cc <print_share_mode>)
at locking/locking.c:330
#2 0x1bc34 in main (argc=1, argv=0x627b0) at utils/status.c:317
(gdb) list
631 (shm_share_mode_entry *)
632 shmops->offset2addr(file_scanner_p->share_mode_entries);
633
634 while(entry_scanner_p != 0) {
635
636 if (process_exists(entry_scanner_p->e.pid)) {
637 fn(&entry_scanner_p-&...