Greetings:
With some tweaks (no pthreads, missing includes, reordering includes,
etc) I was able to build Ver 0.8.14 on OpenBSD/sparc 3.2, gcc 2.95.3.
When attempting to run the executable for the first few times, I got
the unresolved symbol messages other OpenBSD users have posted to this
list while 'ser' is loading modules; however this behavior vanished
spontaneously and now ser simply segfaults and dumps core after about
five seconds (Sun sparc IPX host).
OpenBSD 3.2 doesn't have 'pthreads' but instead has a similar 'pth'
package; 'ser' was built using SysV semaphores instead.
`ser -V`:
version: 0.8.14 (sparc/openbsd)
flags: STATS:Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, DNS_IP_HACK,
SHM_MEM, SHM_MM AP, PKG_MALLOC, F_MALLOC MAX_RECV_BUFFER_SIZE 262144,
MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535
@(#) $Id: main.c,v 1.168.4.3 2004/06/28 15:41:21 andrei Exp $
main.c compiled on 13:32:17 Nov 17 2004 with gcc 2.95
'ser -c' also segfaults but first reports:
0(26788) WARNING: could not read from /dev/random (5)
0(26788) ERROR: shm_mem_init: could not initialize lock
Backtrace of the core file from running 'ser' with an empty 'ser.cfg':
This GDB was configured as "sparc-unknown-openbsd3.2"...
(no debugging symbols found)...
Core was generated by `ser'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libc.so.28.5...(no debugging symbols found)...
done.
Reading symbols from /usr/libexec/ld.so...(no debugging symbols
found)...done.
#0 0x9ee88 in lock_destroy ()
(gdb) bt
#0 0x9ee88 in lock_destroy ()
#1 0x9ede3 in shm_mem_destroy ()
#2 0x9e80b in shm_mem_init_mallocs ()
#3 0x9ea13 in shm_mem_init ()
#4 0x9d783 in init_shm_mallocs ()
#5 0x3acb7 in main ()
#6 0x118df in ___start ()
Anyone care to help?
All replies much appreciated.
Michael Grigoni
Cybertheque Museum