Hi again,
Well, here is what I got. Once again, I only get this when trying to run
on a privilaged port (like 80). The server runs fine on port 8000 I am
starting the server as root and having it suid to user www and group www:
[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'm going to to post a bug report too, but I thought I would just put
it on here as well in case it might be something really simple.
Thanks,
Mike
On Mon, Jun 25, 2001 at 10:24:24AM -0400, Scott Goodwin wrote:
> A segfault occurs when the process tries to read or write outside of its
> memory area. This can be caused by an uninitialized pointer that you then
> try to use, or a pointer that for some other reason is pointing to an area
> outside of its bounds.
>
>
> > Ok. Thanks. I probably am not good enough with C to be able to fix it
> > myself, but hopefully I can find it with gdb and provide enough
> > information for someone else to be able to fix it if I can give a detailed
> > bug report.
>
>
> I'm still pretty pathetic with C. I'm glad you're going to try to find it
> and fix it as you'll undoubtably learn a lot from the experience. I
> certainly have.
>
>
>
> /s.
>
