| To: | PCP <pcp@xxxxxxxxxxx> |
|---|---|
| Subject: | errors from socket code on Mac OS X |
| From: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
| Date: | Wed, 6 Jul 2016 05:53:41 +1000 |
| Delivered-to: | pcp@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 |
I'm seeing this ... [DATE] pmcd(PID) Error: auxconnect.c:__pmSockAddrInit: Invalid address family: 0 [DATE] pmcd(PID) Error: auxconnect.c:__pmSockAddrCompare: Invalid address family: 0 in about half the failing tests on Mac OS X. Does anyone know how or why we'd be traversing the libpcp socket code for an AF of 0? Seems like a missing or broken guard somewhere higher up the call stack, but I have not been able to diagnose this, so I'm seeking assistance from those who know more. Thanks for any hints or suggestions. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Bug 1100] libpcp interp.c crash on archive scan, bugzilla-daemon |
|---|---|
| Next by Date: | Re: [pcp] errors from socket code on Mac OS X, Dave Brolley |
| Previous by Thread: | [Bug 1100] libpcp interp.c crash on archive scan, bugzilla-daemon |
| Next by Thread: | Re: [pcp] errors from socket code on Mac OS X, Dave Brolley |
| Indexes: | [Date] [Thread] [Top] [All Lists] |