From: Noah Lavine <noah.b.lavine@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: Bug in Guile's Posix Networking
Date: Sat, 12 Feb 2011 16:00:54 -0500 [thread overview]
Message-ID: <AANLkTinjkxsg9d8V14U7FiRuKs9KMafM0ggX0QP_Qj_T@mail.gmail.com> (raw)
In-Reply-To: <m3bp2h9dfd.fsf@unquote.localdomain>
I tried the test program
(define addr (inet-aton "127.0.0.1"))
(define sockaddr (make-socket-address AF_INET addr 8080))
(define sock (socket PF_INET SOCK_STREAM 0))
(setsockopt sock SOL_SOCKET SO_REUSEADDR 1)
(bind sock sockaddr)
And got the same error. I also tried changing the port to 9000 and it
still happened.
Noah
On Sat, Feb 12, 2011 at 3:59 PM, Andy Wingo <wingo@pobox.com> wrote:
> On Sat 12 Feb 2011 21:33, Noah Lavine <noah.b.lavine@gmail.com> writes:
>
>>> Does guile --listen work? It appears to use a slightly different way to
>>> set up the sockaddr.
>>
>> Oddly enough, it worked the first time I tried it (at least enough to
>> get to a REPL - I didn't try to netcat over to it), but failed the
>> second and third times.
>
> Would that be an SO_REUSEADDR-related issue?
>
> Musing,
>
> Andy
> --
> http://wingolog.org/
>
prev parent reply other threads:[~2011-02-12 21:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 6:28 Bug in Guile's Posix Networking Noah Lavine
2011-02-07 23:49 ` Andreas Rottmann
2011-02-12 20:47 ` Noah Lavine
2011-02-12 21:02 ` Andy Wingo
2011-02-12 21:35 ` Noah Lavine
2011-02-12 22:00 ` Andy Wingo
2011-02-13 1:22 ` Noah Lavine
2011-02-13 1:45 ` Noah Lavine
2011-02-13 2:22 ` Noah Lavine
2011-02-13 3:00 ` Noah Lavine
2011-02-13 5:42 ` Ken Raeburn
2011-02-13 13:55 ` Noah Lavine
2011-02-13 13:57 ` Noah Lavine
2011-02-13 18:34 ` Ken Raeburn
2011-02-13 20:07 ` Andy Wingo
2011-02-13 20:10 ` Noah Lavine
2011-02-13 20:34 ` Noah Lavine
2011-02-13 21:10 ` Andy Wingo
2011-02-13 20:04 ` Andy Wingo
2011-02-12 11:26 ` Andy Wingo
2011-02-12 20:33 ` Noah Lavine
2011-02-12 20:59 ` Andy Wingo
2011-02-12 21:00 ` Noah Lavine [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTinjkxsg9d8V14U7FiRuKs9KMafM0ggX0QP_Qj_T@mail.gmail.com \
--to=noah.b.lavine@gmail.com \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).