Wrong traces for connected sockets of socketpair with -ff option

Zhouyang Jia jiazhouyang09 at gmail.com
Wed Sep 12 20:47:09 UTC 2018

Hi everyone,

I might come cross a bug for syscall 'socketpair' with option -ff.

When using -ff, strace is supposed to display the ip:port associated with
the sockfd.

According to my understanding, connected sockets should look like:
socketpair(AF_UNIX, SOCK_STREAM, 0, [27<UNIX:[7162769->7162770]>,
28<UNIX:[7162770->7162769]>]) = 0

The syscall 'socketpair' always generates connected socket, but somehow,
strace also generates the following trace:
socketpair(AF_UNIX, SOCK_STREAM, 0, [223<UNIX:[7162686]>,
224<UNIX:[7162687]>]) = 0
which looks like connectless sockets.

This happens everytime.
To triger this, by using $strace -f -yy -o chromium chromium-browser

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20180912/dd9fbe2c/attachment.html>

More information about the Strace-devel mailing list