guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug in Guile's Posix Networking


From: Andy Wingo
Subject: Re: Bug in Guile's Posix Networking
Date: Sat, 12 Feb 2011 23:00:05 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)

Hi Noah,

On Sat 12 Feb 2011 22:35, Noah Lavine <address@hidden> writes:

> socket(0x2, 0x1, 0x0)          = 73 0                    ; make a socket -
> INET family, SOCK_STREAM, internet protocol; we got one with
> descriptor 73
> fcntl(0x49, 0x3, 0x0)          = 2 0                      ; get flags for
> file descriptor 49. result 2 probably means it is read and writable.
> lseek(0x49, 0x0, 0x1)          = -1 Err#29             ; errno 29 is "illegal 
> seek"
> setsockopt(0x49, 0xFFFF, 0x4)          = 0 0      ; setsockopt on descriptor 
> 49
> bind(0x49, 0x100709EE0, 0x10)          = -1 Err#49  ; bind descriptor 49.
> errno 49 is "protocol driver not attached"
>
> ;; And now there's already been an error, and we'll backtrace it.
> write(0x2, "Backtrace:\n\0", 0xB)              = 11 0
> ...
>
> It seems to me that the strangest issue is that socket() return file
> descriptor 73, but the script then did system calls on file descriptor
> 49. Does anyone know a reason that would happen?

#x49 is 73 :)

Could the lseek could be the problem?

A
-- 
http://wingolog.org/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]