On Sat, Nov 07, 2009 at 06:19:04AM -0600, Drake Wilson wrote:
>
> When displaying a sockaddr_in6 structure passed to a system call, all
> the components of the structure have field labels except sin6_addr.
> This is inconsistent with the rest of the structure displays, and
> particularly is inconsistent with the display of sockaddr_in.
>
> Example (line-wrapped, treat \n[ \t]+ as a single space):
> bind(4, {sa_family=AF_INET6, sin6_port=htons(15055),
> inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=0,
> sin6_scope_id=0}, 28) = 0
strace displays
sin_addr=inet_addr("127.0.0.1")
for AF_INET, and
inet_pton(AF_INET6, "::1", &sin6_addr)
for AF_INET6. I see no inconsistency so far.
> Example:
> connect(3, {sa_family=AF_FILE, path="/home/drake/.paneliy"}, 110) = 0
>
> Displaying a sockaddr_un structure uses the field name "path" rather
> than "sun_path", which is inconsistent with the other sockaddr
> structures.
I agree, it should be sun_path= instead of path=.
--
ldv
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
