Pino Toscano, le Sun 04 Dec 2011 16:45:20 +0100, a écrit :
> Alle domenica 4 dicembre 2011, Samuel Thibault ha scritto:
> > Pino Toscano, le Sun 04 Dec 2011 13:14:52 +0100, a écrit :
> > > while debugging, I apparently stumbled upon a bug of getsockname()
> > > for a bound unix socket, as also the
Alle domenica 4 dicembre 2011, Samuel Thibault ha scritto:
> Pino Toscano, le Sun 04 Dec 2011 13:14:52 +0100, a écrit :
> > while debugging, I apparently stumbled upon a bug of getsockname()
> > for a bound unix socket, as also the attached test program shows:
> > sun_path is left unfilled, as also
Pino Toscano, le Sun 04 Dec 2011 13:14:52 +0100, a écrit :
> while debugging, I apparently stumbled upon a bug of getsockname() for a
> bound unix socket, as also the attached test program shows: sun_path is
> left unfilled, as also the comment of S_socket_whatis_address() in
> hurd/pflocal/pf.c
Hi,
while debugging, I apparently stumbled upon a bug of getsockname() for a
bound unix socket, as also the attached test program shows: sun_path is
left unfilled, as also the comment of S_socket_whatis_address() in
hurd/pflocal/pf.c would suggest.
There's also another possibly weird behaviour
