Bugs item #437414, was opened at 2001-06-29 10:58
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=103152&aid=437414&group_id=3152
Category: Configuration: Server
Group: aolserver3_4
Status: Open
Resolution: None
>Priority: 5
Submitted By: Michael Urban (simba5)
Assigned to: Nobody/Anonymous (nobody)
Summary: Segfault on FreeBSD 5.0-CURRENT
Initial Comment:
I am having a problem with AOL Server 3.4 causing a
segmentation fault on FreeBSD 5.0-CURRENT as soon as I
try to start it. It will run fine on port 8000, but it
segfaults anytime I try to start it on port 80. I have
not tested this on the release version of FreeBSD (4.3)
so I am not sure if it is a problem with the server, or
a problem with something in FreeBSD 5.0.
Here is the gdb trace that I get when trying to run the
server on port 80:
[25/Jun/2001:16:30:13][15486.135540736][-main-] Notice:
binder:
listen(205.216.111.20,80) = 15
[25/Jun/2001:16:30:13][15486.135540736][-main-] Notice:
nssock: listening on 205.216.111.20:80
Program received signal SIGSEGV, Segmentation fault.
0x281820ff in ioctl () from /usr/lib/libc_r.so.5
(gdb) bt
#0 0x281820ff in ioctl () from /usr/lib/libc_r.so.5
#1 0x80805df in Ns_SockSetNonBlocking (sock=15) at
sock.c:385
#2 0x2824551a in SockStart (server=0x8145560
"server1",
label=0x8145b10 "nssock", drvDataPtr=0x8171208) at
sock.cpp:474
#3 0x806e326 in NsStartDrivers (server=0x8145560
"server1") at drv.c:225
#4 0x8077491 in Ns_Main (argc=8, argv=0xbfbffadc,
initProc=0x807445c <ServerInit>) at
nsmain.c:697
#5 0x8074448 in main (argc=8, argv=0xbfbffadc) at
main.c:64
#6 0x805ae7f in _start ()
(gdb)
I am starting the server as root and then having it
switch to the user and group "www". Like I said, this
only occurs on port 80 and not on 8000, so I assume it
has to do with privilaged ports.
Any ideas?
Thanks,
Mike
----------------------------------------------------------------------
>Comment By: Michael Urban (simba5)
Date: 2001-06-30 15:40
Message:
Logged In: YES
user_id=257485
I found someone to test this for me on FreeBSD 4.3 and the
server runs fine. This seems to be a bug in the ioctl()
function of FreeBSD 5.0-CURRENT or something. I posted a
message to the FreeBSD CURRENT mailing list regarding the
problem and am awaiting a response from there.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=103152&aid=437414&group_id=3152
