We were trying to kill a thread that had already expired. I put a mutex around it and check.
Also moved the "per port" data to struct "connection_out" since that is already "per_port".
Paul Alfille
On 11/12/06, Christian Magnusson <[EMAIL PROTECTED]> wrote:
The segfault is one of the problem… It only segfaults after you have read a device-page.
owhttpd --foreground --error_level=9 -s 3011 -p 3012
owserver --foreground --error_level=9 --fake 10,10 -p 3011
kill –INT <owserver>
works perfect
owhttpd --foreground --error_level=9 -s 3011 -p 3012
owserver --foreground --error_level=9 --fake 10,10 -p 3011
lynx –source http://localhost:3012/uncached/
kill –INT <owserver>
works perfect..
owhttpd --foreground --error_level=9 -s 3011 -p 3012
owserver --foreground --error_level=9 --fake 10,10 -p 3011
lynx –source http://172.20.1.101:3012/10.67C6697351FF
kill –INT <owserver>
owserver segfaults since the memory/stack is corrupt.
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
