Open Radar

 
Summary:
NSLog, when it reports a log entry to stderr and ASL, uses the wrong values as the thread ID.  This confounds debugging, since tools such as lldb, sample, spindump, Activity Monitor, etc, use the actual thread ID.  (NSLog reports the Mach thread self port name in hex, instead of the thread ID in decimal.)

Steps to Reproduce:
1. Observe stderr of any program that writes to NSLog.  Log entries are formatted as: date time progname[pid:tid] message. Note the tid.
2. Debug the same program in lldb (aka Xcode debugger).  Run the lldb command "thread list". Note the tids.
3. Observe the same program in Activity Monitor, sample, or spindump. Note the thread IDs.

Expected Results:
Thread IDs should be consistent and correct.

Actual Results:
lldb, sample, spindump, and Activity Monitor are consistent (although lldb reports tid in hexadecimal).  NSLog inconsistent is with the other tools.

Version:
OS X 10.9 (13A603)

Notes:
Fix: In CoreFoundation, CFUtilities.c, lines 623 and 624 (as of CF-855.11):
On both lines, change "pthread_mach_thread_np(pthread_self())" to "pthread_threadid_np(NULL, &pthreadThreadId)".
And, while you're there, please change the format specifier "%x" to "%u" -- most other tools use decimal for thread ids, and the other fields in a log message (pid, for example) are decimal.

Configuration:


Attachments: