lldb调试三方App时，经常会The LLDB RPC server has crashed

技能讨论
#1

错误信息如下：

The LLDB RPC server has crashed. The crash log is located in ~/Library/Logs/DiagnosticReports and has a prefix ‘lldb-rpc-server’. Please file a bug and attach the most recent crash log.

出现场景：

比如说，我在调试的过程中发生了崩溃，然后我退出重新attach App，启动lldb
，然后用命令打了一些断点，c之后定会出现这种问题。

请问有知道原因怎么解决的么？

#2 
Crashed Thread:        4  <lldb.process.internal-state(pid=0)>

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000028
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]


Thread 4 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x00007f7fa7518cf0  rcx: 0x000000011198a3d8  rdx: 0x0000070000000801
  rdi: 0x0000000000000000  rsi: 0x00007f7fa7518cf0  rbp: 0x000070000a6d0760  rsp: 0x000070000a6d0760
   r8: 0x00000000007690a2   r9: 0xffffffff00000000  r10: 0x00007f7faad563f0  r11: 0x00007f7faad563f8
  r12: 0x00007f7fa7518cf0  r13: 0x0000000000000006  r14: 0x00000001108eea24  r15: 0x00007f7faa651fe0
  rip: 0x00000001105b83a2  rfl: 0x0000000000010246  cr2: 0x00007fae06f5bcf0
  
Logical CPU:     0
Error Code:      0x02000131
Trap Number:     133

EXC_BAD_ACCESS：此类型是最常见的crash, 通常由于访问了不该访问的内存导致的。

SIGSEGV:通常由于重复释放对象导致。