Todd Fiala wrote:
Hey Matthew,
That 0 parameter to strtoul doesn't quite work like that. The 0
indicates that the input character string determines how the base is
interpreted. So a 0x{hex} will get interpreted base 16, a standard
non-zero-leading set of decimal numbers is base 10, and a 0{octal} is
octal.
Sorry, my bad. I think I jumped the gun here! However, the documentation
in lldb-gdb-remote.txt does state that for qHostInfo:
cputype: is a number that is the mach-o CPU type that is being debugged
(base 10)
but for qProcessInfo:
cputype: the Mach-O CPU type of the process (base 16)
So I wondered whether bases of either message were intended to be
different. That's why I think something is a bit wrong in the docs. Then
I looked at the parsing code, and unfortunately misinterpreted the 0
specification :-(
However, what do you (and others!) think of the discrepancy between the
qHostInfo and qProcessInfo docs?
Matt
Member of the CSR plc group of companies. CSR plc registered in England and
Wales, registered number 4187346, registered office Churchill House, Cambridge
Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
More information can be found at www.csr.com. Keep up to date with CSR on our
technical blog, www.csr.com/blog, CSR people blog, www.csr.com/people, YouTube,
www.youtube.com/user/CSRplc, Facebook,
www.facebook.com/pages/CSR/191038434253534, or follow us on Twitter at
www.twitter.com/CSR_plc.
New for 2014, you can now access the wide range of products powered by aptX at
www.aptx.com.
_______________________________________________
lldb-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
