[lldb-dev] lldb 340.4.119 unable to attach (El Capitan)

Jason Molenda via lldb-dev lldb-dev at lists.llvm.org
Tue Jan 5 12:09:34 PST 2016


> On Jan 5, 2016, at 10:17 AM, Greg Clayton via lldb-dev <lldb-dev at lists.llvm.org> wrote:
> 
> 
>> So how about:
>> 
>> (lldb) run
>> error: developer mode not enabled
> 
> We should be able to do this. The main issue is detecting that the user is in a remote scenario where they don't have access to the UI. A dialog box will be popped up if the user is on the system, but when remotely connected we would need to detect this and return a correct error. This is a little harder as well because "debugserver", our GDB remote protocol debug stub, is what is requesting the debugging privelege. This is a program that is spawned by LLDB as a child process. But is should be able to be done somehow.


I have a low priority Todo to implement this - when I looked into it, it was just a few CF calls and I could retrieve whether developer mode was enabled in debugserver and report that to the user.


More information about the lldb-dev mailing list