Here we see that upath1 is set to /, address is empty and port is non-present. So I'd assume that this was probably a UDS socket that the call was made on, but I have no idea what path it had, as / seems implausible.
I haven't observed many sendto calls in the traces I've seen, but i'd suspect that they may exhibit the same problems.
Some
recvfrom
calls in the buildinject trace show very little helpful data for the address of the object being acted upon.e.g.
Here we see that
upath1
is set to/
,address
is empty andport
is non-present. So I'd assume that this was probably a UDS socket that the call was made on, but I have no idea what path it had, as/
seems implausible.I haven't observed many
sendto
calls in the traces I've seen, but i'd suspect that they may exhibit the same problems.