title: LLDB Show trap opcodes in memory dump
body: <p>I'm wondering if it is possible with LLDB's memory dumper to see trap opcodes in locations where I've just set a beakpoint?
  As I see LLDB is smart enough to shadow trap opcodes with original ones:</p>
  
  <pre><code>(lldb) memory read --format instruction --count 5 0x00000076619b5478
  -&gt;  0x76619b5478: 0xf9401668   ldr    x8, [x19, #0x28]
      0x76619b547c: 0xf9400289   ldr    x9, [x20]
      0x76619b5480: 0xeb09011f   cmp    x8, x9
      0x76619b5484: 0x540000e1   b.ne   0x76619b54a0              ; &lt;+200&gt;
      0x76619b5488: 0xa95d7bf3   ldp    x19, x30, [sp, #0x1d0]
  (lldb) breakpoint set --address 0x76619b5488
  Breakpoint 3: where = libface_detector_v2_jni.so`___lldb_unnamed_symbol20247$$libface_detector_v2_jni.so + 176, address = 0x00000076619b5488
  (lldb) memory read --format instruction --count 5 0x00000076619b5478
  -&gt;  0x76619b5478: 0xf9401668   ldr    x8, [x19, #0x28]
      0x76619b547c: 0xf9400289   ldr    x9, [x20]
      0x76619b5480: 0xeb09011f   cmp    x8, x9
      0x76619b5484: 0x540000e1   b.ne   0x76619b54a0              ; &lt;+200&gt;
      0x76619b5488: 0xa95d7bf3   ldp    x19, x30, [sp, #0x1d0]
  </code></pre>
  
  <p>Here I set a break at <code>0x76619b5488</code> but dumper still shows original instruction at that place.
  <code>help memory read</code> has no hints about how one could see trap opcodes.</p>
  
  <p>Any ideas?</p>
  
  <p>P.S. It is an LLDB bundled with Android SDK, claimed version: <code>7.0.0</code>. Target is an Android Aarch64.</p>