Re: [Clorb-devel] clorb-0.2 on CMUCL and CLISP

[Lennart S. <le...@ly...>]

Brad Chapman <cha...@ar...> writes:

> * (hello-client :file "hw.ior")
> Error in function CLORB::UNMARSHAL-GIOP-HEADER:  Not a GIOP message
> 
> Restarts:
>   0: [ABORT] Return to Top-Level.
> 
> Debug  (type H for help)
> 
> (CLORB::UNMARSHAL-GIOP-HEADER
>  #S(CLORB::BUFFER
>       :OCTETS #(0 0 0 0 0...)

The client seems to have read in a lot of zeros from the stream. That
is strange. Could be some error handling that is wrong.

Any way, this is probably a consequence on the error on the server
side.


> The server also crashes when this occurs, with the following backtrace:
> 
> * (run-hello :file "hw.ior")
> Compiling LAMBDA (#:G1518 #:G1519 #:G1520 #:G1521 #:G1524 #:G1525):
> Compiling Top-Level Form:
> ;;; Acception tcp connection: 6
> ;;  - to stream: #<Stream for descriptor 6>
> ;; Receive (60)
> 
> Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER:
>    -1 is not of type (MOD 536870911)
> 
> Restarts:
>   0: [ABORT] Return to Top-Level.
> 
> Debug  (type H for help)
> 
> (CLORB::UNMARSHAL-STRING
>  #S(CLORB::BUFFER
>       :OCTETS #(71 73 79 80 1...)
>       :POSITION 32
>       :BYTE-ORDER 1
>       :START-POS 0))
> Source:
> ; File: /usr/home/chapmanb/clorb-0.2/clorb-unmarshal.lisp
> (MAKE-STRING LEN)

This is from make-string. It must be LEN that is -1. And it must be
the operation name it is trying to unmarshal. I can't figure out why
the length is -1.

What kind of machine and OS are you running on? Could you try and load
the "test-marshal.lisp" and see if it produces any errors?



> clisp
> -----
> On clisp, I get an error immediately upon trying to start up the server,
> and it gives the following trace.
> 
> [7]> (run-hello :file "hw.ior")
> 
> *** - UNIX error 49 (EADDRNOTAVAIL): Can't assign requested address

I wonder what that error code means. It is probably not the same as
"address already in use". Could you try to find a description of this
error. The man-pages socket(2), bind(2) and listen(2) might contain
something. The Linux man-pages doesn't (they say "SVr4 documents
additional EADDRNOTAVAIL, EADDRINUSE, and ENOSR general error
conditions").

-- 
Lennart Staflin  <le...@ly...>