[lldb-dev] lldb issues on MacOS

[jingham at apple.com]

debugserver may also be exiting unexpectedly.  You could try running another copy of lldb, and doing an "attach --wait" for debugserver, then setting a breakpoint on exit, and see why it is exiting.

The MI interface uses LLDB through the SB API interfaces.  So it does not need to be built with a specific version of lldb to be used.  If you want to use it you should be able to just make it into a dylib, and then include it in whatever app you are making.  I don't know what the plans for it in LLVM releases are, however.

Jim

> On Nov 18, 2014, at 1:23 AM, Nikolay Koldunov <nikolay.koldunov at oracle.com> wrote:
> 
> There was nothing connected to debugserver in ~/Library/Logs/DiagnosticReports.
> 
> The only thing I could see was:
> 
> (lldb) r
> error: process exited with status -1 (lost connection)
> 'r' and 'run' are aliases that default to launching through a shell.
> Try launching without going through a shell by using 'process launch'.
> (lldb) process launch
> error: process exited with status -1 (lost connection)
> 
> If you tell me where to search I'll be glad to provide you with some extra info.
> 
> We are going to support the MI functionality and I wonder whether you can tell me which LLVM release will contain lldb-mi?
> 
> 
> On 11/12/14 09:41 PM, jingham at apple.com wrote:
>> Look in the Console log to see what debugserver says when it tries to attach.  "lost connection" isn't typically what debugserver would say if the problem is a task-for-pid denial (i.e. a code signing problem.)  In that case, you usually see something like "could not get task for pid..."  lost connection means debugserver has unexpectedly quit for some reason (crashed or exited unexpectedly...)  Anyway, if you look in the console log, if it is a code signing problem you will see error messages from debugserver saying it failed to get the task for pid whatever.
>> 
>> Also look in ~/Library/Logs/DiagnosticReports for any crash logs from debugserver.
>> 
>> Jim
>> 
>> 
>>> On Nov 12, 2014, at 3:39 AM, Nikolay Koldunov<nikolay.koldunov at oracle.com>  wrote:
>>> 
>>> I've signed it and it consequently works fine in the local case. The problem appears when I try to debug via ssh.
>>> 
>>> On 11/12/14 12:10 PM, Jason Molenda wrote:
>>>> Did you set up the lldb_codesign certificate on your system?  v. docs/code-signing.txt .  It sounds like your debugserver binary isn't signed with the lldb_codesign cert, or that cert isn't in the necessary keychains.
>>>> 
>>>> J
>>>> 
>>>> 
>>>>> On Nov 12, 2014, at 12:24 AM, Nikolay Koldunov<nikolay.koldunov at oracle.com>   wrote:
>>>>> 
>>>>> The problem still remains(
>>>>> 
>>>>> # sudo /usr/sbin/DevToolsSecurity --enable
>>>>> Developer mode is already enabled.
>>>>> 
>>>>> (lldb) r
>>>>> error: process exited with status -1 (lost connection)
>>>>> 'r' and 'run' are aliases that default to launching through a shell.
>>>>> Try launching without going through a shell by using 'process launch'.
>>>>> (lldb) process launch
>>>>> error: process exited with status -1 (lost connection)
>>>>> 
>>>>> On 11/11/14 09:07 PM, Greg Clayton wrote:
>>>>>> Do this first in your ssh session:
>>>>>> 
>>>>>> sudo /usr/sbin/DevToolsSecurity --enable
>>>>>> 
>>>>>> Then try running lldb.
>>>>>> 
>>>>>>> On Nov 11, 2014, at 2:20 AM, Nikolay Koldunov<nikolay.koldunov at oracle.com>    wrote:
>>>>>>> 
>>>>>>> Thank You!
>>>>>>> 
>>>>>>> This helped in the local case. But I'm still unable to run lldb in either console or mi mode via ssh. Is this possible?
>>>>>>> 
>>>>>>> On 11/ 6/14 09:35 AM, Eran Ifrah wrote:
>>>>>>>> I have this big comment in my code that will help you:
>>>>>>>> 
>>>>>>>> // On OSX, debugserver executable must exists otherwise lldb will not work properly
>>>>>>>> // we ensure that it exists by checking the environment variable LLDB_DEBUGSERVER_PATH
>>>>>>>> 
>>>>>>>> In other words: set the environment variable LLDB_DEBUGSERVER_PATH to point to debugserver executable (you should have it installed with your XCode)
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On Fri, Oct 31, 2014 at 3:20 PM, Nikolay Koldunov<nikolay.koldunov at oracle.com>    wrote:
>>>>>>>> Hi All!
>>>>>>>> 
>>>>>>>> I've just built lldb and lldb-mi from the trunk sources on MacOS and faced these issues:
>>>>>>>> 1). lldb was unable to run target (error: process launch failed: unable to locate debugserver)
>>>>>>>> 2). lldb-mi was unable to run target too (Command 'exec-run'. Invalid process during debug session)
>>>>>>>> 
>>>>>>>> I followed your instructions about code signing.
>>>>>>>> 
>>>>>>>> What should I do or check to proceed?
>>>>>>>> 
>>>>>>>> Regards,
>>>>>>>> Nikolay
>>>>>>>> _______________________________________________
>>>>>>>> lldb-dev mailing list
>>>>>>>> lldb-dev at cs.uiuc.edu
>>>>>>>> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> -- 
>>>>>>>> Eran Ifrah,
>>>>>>>> Author of codelite, a cross platform open source C/C++ IDE: http://www.codelite.org
>>>>>>>> CodeLite IDE Blog: http://codeliteide.blogspot.com/
>>>>>>> _______________________________________________
>>>>>>> lldb-dev mailing list
>>>>>>> lldb-dev at cs.uiuc.edu
>>>>>>> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>>>>> _______________________________________________
>>>>> lldb-dev mailing list
>>>>> lldb-dev at cs.uiuc.edu
>>>>> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>>> _______________________________________________
>>> lldb-dev mailing list
>>> lldb-dev at cs.uiuc.edu
>>> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>