I'm going to have to think about this a bit. A number of the fprintf's are immediately followed by an abort() and serve to provide the user better diagnostic information. Changing those into comments may be the simple solution that helps people who run into issues.

Some of them are informational, the operation is indicated as failing (gracefully) but an informational message is provided. I'm tempted to change these into some form of assert.

Looking around the code for other examples of handling errors, I came across uv__stream_recv_cmsg() in https://github.com/joyent/libuv/blob/master/src/unix/stream.c
```
      if (cmsg->cmsg_type != SCM_RIGHTS) {
      fprintf(stderr, "ignoring non-SCM_RIGHTS ancillary data: %d\n",
          cmsg->cmsg_type);
      continue;
    }
```
which seems to be providing informational output and continuing.

I may need more guidance on when information messages are ok.