Yep - with HP-UX running on 64-bit Itanium, and using the 64-bit data model. The side effect of having the "long val" in the union definition is that it'll have corrupted the mutex/semaphore while creating the proc_mutex itself (proc_mutex_sysv_create). On HP-UX, the symptom was that the listener_thread hangs while doing a SAFE_ACCEPT.
AFAICT, the only exception is win32, which retains the 32 bit int, 64 bit memory
pointer, 64 bit 'INT_PTR' meaning that it could wrap an int or pointer.
This appears to apply to _NO_ unix architectures, so int should be correct. We could create an ap_intptr_t that does the same, with;
typedef union ap_intptr_t {
int i;
int *p;
} ap_intptr_t;and take ap_intptr_t or sizeof(ap_intptr_t) when we need an object that safely maps either and both.
Bill
