[lldb-dev] LLDB code signing
andrey.zaytsev at jetbrains.com
Wed Jul 11 05:37:01 PDT 2012
Copying debugserver is a good idea. But what happens if it is changed and Xcode build with new version is not available yet? We can't upgrade our product to newer version of LLDB that Xcode uses in this case.
Maybe we can install our certificate which was used for code signing of LLDB with AppCode and ask user to trust it in order to use debugger with AppCode?
On 10.07.2012, at 3:54, Greg Clayton wrote:
> If you don't require any changes to debugserver, you can always copy the debugserver binary from the LLDB.framework that comes with the latest Xcode since that will be code signed by Apple. Currently debugserver is the only thing that needs to be codesigned.
> The issue you are seeing is indeed due to incorrect code signing.
> On Jul 9, 2012, at 11:18 AM, Andrey Zaytsev wrote:
>> We are thinking of bundling custom LLDB build with our product. What should we do with code signing? I just moved built lldb from one of my macs to another and it reports error: "initial process state wasn't stopped: exited".
>> lldb-dev mailing list
>> lldb-dev at cs.uiuc.edu
More information about the lldb-dev