That would be fine. We will need to track down any printf statements (or similar Printf stream calls) that use thread IDs and make sure to specify:
"0x%4.4llx" instead of our current default of: "0x%4.4x" On Apr 1, 2011, at 2:13 PM, Matthew Dempsky wrote: > On Fri, Apr 1, 2011 at 1:39 PM, Stephen Wilson <[email protected]> wrote: >> So I think the main question is: does having the full 64 bit pointer as >> an ID give useful info to the developers using user-space threads? > > Is there a reason not to just make the thread ID a 64-bit value and be > done with it? Seems like doing anything else is over-engineering the > problem. _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
