In case anyone else is interested I just learned that this is a known bug in lldb which was fixed recently, but evidently the fix has not yet made its way into Apple’s build. I got the following info from Enrico Granata on StackOverflow (see: http://stackoverflow.com/a/33114721/253056 <http://stackoverflow.com/a/33114721/253056>):
> This issue has been fixed in open source LLDB, as revision 243893 > (http://llvm.org/viewvc/llvm-project?view=revision&revision=243893 > <http://llvm.org/viewvc/llvm-project?view=revision&revision=243893>) Paul > On 13 Oct 2015, at 11:28, Paul Russell <[email protected]> wrote: > > I cant seem to get lldb’s “memory find” command to work with the -e option. > > I've found that the -s option can be made to work, e.g. like this: > > (lldb) me fi -s "f" -- ptr ptr+8192*256 > Your data was found at location: 0x11033e20c > 0x11033e20c: 66 bb 58 07 d0 b7 32 7d ff 7f 00 00 66 5b e7 82 f.X...2}....f[.. > > But it looks like the -e option (which is what I need in this instance) is > broken, e.g.: > > (lldb) me fi -e 255 -- ptr ptr+8191*256 > error: expression evaluation failed. pass a string instead? > > Trying to coax the -s option into accepting an escaped hex or decimal value > doesn't seem to work either, unfortunately: > > (lldb) me fi -s "\xff" -- ptr ptr+8191*256 > Your data was not found within the range. > > (lldb) me fi -s "\255" -- ptr ptr+8191*256 > Your data was not found within the range. > > Am I missing something in the way I’m trying to use the -e option ? > > Paul >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
