Hello Lutz,
little remark..
It seems the "broken pipe" is still there.
It does NOT appear running from within console mode,
but running from command line its still there...see below...
> (load "test")
(4)
(5 4)
(5 4)
(5 4)
(4)
true
> (exit)
bash-2.05b$ newlisp test
(4)
(5 4)
(5 4)
(5 4)
Broken pipe
bash-2.05b$
Norman.
I am not sure how to replicate this, what's the procedure?
Lutz
Hello Lutz,
Here is the procedure:
Run the following script "test"
---
(set 'server (net-listen 1234 "10.10.10.11" ))
(println (net-sessions))
(set 'conn (net-accept server))
(println (net-sessions))
(until (net-error)
(sleep 3000)
(net-send conn "abc" )
(println (net-sessions)))
---
$ newlisp test
(4)
** Now start a separate telnet towards 10.10.10.11 1234
(5 4)
** Here is the connect from the client telnet
(5 4)
*** After the 1st receipt "abc" on the client site press "^]" and quit the telnet
(5 4)
Broken pipe
Hope yuo can reproduce it, running the script from within console of newlisp (load "test")
there is a nice ( catch or true )of the error as slown below:
> (load "test")
(4)
(5 4)
*** quit the telnet client after 1st receipt of "abc"
(5 4)
(5 4)
(4)
true
>
I think its related to a timing issue under the console-mode weather its a 'true or net-error
But running from the shell it always generates a Broken Pipe. Hope yuo can reproduce it...
regards,
Norman.
Hello Norman,
thanks for the details, the signal handlers where initialized to late. A fixed version is in:
http://newlisp.org/download/development/newlisp_7507.tgz
works fine on Linux Mandrake 9.2 on Windows it also affected the Ctrl-C handler when running scriptfiles.
Lutz
7.5.7 Runs fine !
thanks...
Norman.