[lldb-dev] lldb patches for OpenBSD

Jim Ingham jingham at apple.com
Fri Apr 1 15:00:28 PDT 2011

gdb has some functions like "paddr_nz" which take the basic address types and converts them to whatever string looks good for that type.  Might be nice to do something like that instead of hard-coding format strings in logs everywhere and then having to go change them when we end up needing to change the type...


On Apr 1, 2011, at 2:36 PM, Greg Clayton wrote:

> 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 <wilsons at start.ca> 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
> lldb-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev

More information about the lldb-dev mailing list