> On Jun 11, 2014, at 11:35 PM, Matthew Gardiner <[email protected]> wrote: > > 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)
FWIW I think I might have added the base10/base16 notes to the docs. I did it based on how the existing implementation worked; it's unfortunate that they behave differently. For that matter, it's unfortunate that we don't require 0x before all base16 numbers in gdb-remote protocol. _______________________________________________ lldb-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
