Re: running test suite in mac osx error: IP bind error: Address

2011-06-10 Thread Edwin Eyan Moragas
Hi Alex,

On Fri, Jun 10, 2011 at 1:16 PM, Alexander Burger a...@software-lab.de wrote:
 Hi Edwin,

 any chance ideas on how to fix this on osx?

 In which situation does this error appear?

not sure which specific one. but the ouput's here:

eyan@faya $ $(/bin/pwd)/p lib/test.l -bye +
[test/lib.l:5] !? (port T )
IP bind error: Address already in use
?




   # lsof -i :port


was using netstat and the lsof invocation above. the port's ok.

this also happens in obsd by the way.

btw, if it is significant, i'm sticking with 3.0.5. i tried this with
the current version too and it's the same story.

/e
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe


Re: running test suite in mac osx error: IP bind error: Address

2011-06-10 Thread Alexander Burger
Hi Edwin,

 eyan@faya $ $(/bin/pwd)/p lib/test.l -bye +
 [test/lib.l:5] !? (port T )
 IP bind error: Address already in use

Oh, I see. This are the unit tests, and it is the place where it tries
to bind to a UDP port.

So it seems the UDP handling of PicoLisp doesn't work under Mac OS (and
OpenBSD, where Mac OS is derived from, iirc).

In the past, we have tested it a lot under FreeBSD, and couldn't see any
problems with that.

Is there anybody who can debug it under Mac OS or OpenBSD?


 btw, if it is significant, i'm sticking with 3.0.5. i tried this with
 the current version too and it's the same story.

No problem, I think. The network stuff didn't change recently.

What comes to my mind, though: PicoLisp is not IPv6 ready yet (see
previous discussions here). Could this be a reason?

Cheers,
- Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe


Re: running test suite in mac osx error: IP bind error: Address

2011-06-10 Thread Edwin Eyan Moragas
Hi Alex,

On Fri, Jun 10, 2011 at 4:05 PM, Alexander Burger a...@software-lab.de wrote:
 Hi Edwin,

 eyan@faya $ $(/bin/pwd)/p lib/test.l -bye +
 [test/lib.l:5] !? (port T )
 IP bind error: Address already in use

 Oh, I see. This are the unit tests, and it is the place where it tries
 to bind to a UDP port.

 So it seems the UDP handling of PicoLisp doesn't work under Mac OS (and
 OpenBSD, where Mac OS is derived from, iirc).

check this.


 In the past, we have tested it a lot under FreeBSD, and couldn't see any
 problems with that.

 Is there anybody who can debug it under Mac OS or OpenBSD?

i'll be on it. not sure about time frame tho since i'm diddling with
an app at the moment. looks like i'm the only one running it on obsd
so i guess it's not an urgent issue. :)



 btw, if it is significant, i'm sticking with 3.0.5. i tried this with
 the current version too and it's the same story.

 No problem, I think. The network stuff didn't change recently.

 What comes to my mind, though: PicoLisp is not IPv6 ready yet (see
 previous discussions here). Could this be a reason?

probably not. IPv6 not enabled in my obsd setup.

thanks Alex. was silly i should have mentioned running the test suite
in my first email.

/e
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe


Re: running test suite in mac osx error: IP bind error: Address

2011-06-10 Thread Alexander Burger
Hi Edwin,

 i'll be on it. not sure about time frame tho since i'm diddling with

Great!

 an app at the moment. looks like i'm the only one running it on obsd
 so i guess it's not an urgent issue. :)

We are now discussing it also in IRC. ckeen checked on his BSD system,
and the UDP binding worked. We ran into other problems, though, the
signal() calls don't seem to work :(

Too bad ...

Cheers,
- Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe


Re: running test suite in mac osx error: IP bind error: Address

2011-06-10 Thread Edwin Eyan Moragas
On Fri, Jun 10, 2011 at 5:43 PM, Alexander Burger a...@software-lab.de wrote:
 Hi Edwin,

 i'll be on it. not sure about time frame tho since i'm diddling with

 Great!

 an app at the moment. looks like i'm the only one running it on obsd
 so i guess it's not an urgent issue. :)

 We are now discussing it also in IRC. ckeen checked on his BSD system,
 and the UDP binding worked. We ran into other problems, though, the
 signal() calls don't seem to work :(

ctrl-c when repl is running is not working on obsd. not sure if this
is related to the signal() call. it's in my todo list.


 Too bad ...

 Cheers,
 - Alex
 --
 UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe


Re: running test suite in mac osx error: IP bind error: Address

2011-06-10 Thread Alexander Burger
Hi Edwin,

 ctrl-c when repl is running is not working on obsd. not sure if this
 is related to the signal() call. it's in my todo list.

Yes, that's the same case. The whole complex of catching signals.
We are at it ... :)

Cheers,
- Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe


Re: running test suite in mac osx error: IP bind error: Address

2011-06-10 Thread Alexander Burger
Hi Edwin,

 We are at it ... :)

We've got it!! Thanks to ckeen! :)

There were actually two problems with the OpenBSD version:

1. Signal handling was wrong. There was the possibility of an array
   out-of-bound access because of a non-portable max signal number.

2. UDP handling was indeed wrong. The port was used twice during the
   tests, and not closed in between. It is just that Linux doesn't give
   an error in that case.

Both should be fixed now.

If you like to try, please download the latest version, e.g.

   wget software-lab.de/picoLisp.tgz


Many thanks for your bug report!

Cheers,
- Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe


Re: running test suite in mac osx error: IP bind error: Address

2011-06-10 Thread Edwin Eyan Moragas
whopee!

thanks Alex and ckeen!

On Fri, Jun 10, 2011 at 8:24 PM, Alexander Burger a...@software-lab.de wrote:
 Hi Edwin,

 We are at it ... :)

 We've got it!! Thanks to ckeen! :)

 There were actually two problems with the OpenBSD version:

 1. Signal handling was wrong. There was the possibility of an array
   out-of-bound access because of a non-portable max signal number.

 2. UDP handling was indeed wrong. The port was used twice during the
   tests, and not closed in between. It is just that Linux doesn't give
   an error in that case.

 Both should be fixed now.

 If you like to try, please download the latest version, e.g.

   wget software-lab.de/picoLisp.tgz


 Many thanks for your bug report!

 Cheers,
 - Alex
 --
 UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe


Re: running test suite in mac osx error: IP bind error: Address

2011-06-10 Thread Edwin Eyan Moragas
downloaded and ran the unit tests

now runs fine on osx snow leopard and obsd 4.8 32 bit.

thanks a bunch again guys!

On Fri, Jun 10, 2011 at 9:01 PM, Edwin Eyan Moragas e...@yndy.org wrote:
 whopee!

 thanks Alex and ckeen!

 On Fri, Jun 10, 2011 at 8:24 PM, Alexander Burger a...@software-lab.de 
 wrote:
 Hi Edwin,

 We are at it ... :)

 We've got it!! Thanks to ckeen! :)

 There were actually two problems with the OpenBSD version:

 1. Signal handling was wrong. There was the possibility of an array
   out-of-bound access because of a non-portable max signal number.

 2. UDP handling was indeed wrong. The port was used twice during the
   tests, and not closed in between. It is just that Linux doesn't give
   an error in that case.

 Both should be fixed now.

 If you like to try, please download the latest version, e.g.

   wget software-lab.de/picoLisp.tgz


 Many thanks for your bug report!

 Cheers,
 - Alex
 --
 UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe


--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe


Re: running test suite in mac osx error: IP bind error: Address

2011-06-09 Thread Alexander Burger
Hi Edwin,

 any chance ideas on how to fix this on osx?

In which situation does this error appear?

An IP bind error occurs if a port is already used by (bound to) some
other process. This either happens if another, already running,
application uses the same port, or if you start your app a second time
while the first instance is still listening on that port.

You can find out if a port is used by some process (best as 'root', to
see all):

   # lsof -i :port

e.g.

   # lsof -i :80
   COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
   httpGate 1660 root3u  IPv4   4618  0t0  TCP *:www (LISTEN)

or

   # lsof -i :8080
   COMMAND  PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
   pil 8649  abu   17u  IPv4 2560247  0t0  TCP *:http-alt (LISTEN)

Cheers,
- Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe