Mike writes: >After looking at the definition file, I see that I was correct. The >POSIX PID actually is three fields: a sign bit, a reuse counter, and >the PIN. Of course, the POSIX PID is supposed to be an opaque data >type. So, if you write code that decomposes this number, it's subject >to future breakage. How about an API a la map_pid_to_pin_of_the_POSIX_variety() :-) that will take care of the "potential for change" issues? gdb needs to be able to decompose (and perhaps recompose) pins from POSIX pids and if I can avoid having to remember "one more thing" during each port, that'll help! :-) Regards, M.