On Jul 11, 2012, at 5:37 AM, Andrey Zaytsev wrote: > Hi! > 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.
Indeed. > 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? That sounds good, but I am not sure how to do this. If you figure this out, please let us know how and what you did! Greg > > > 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. >> >> Greg >> >> >> On Jul 9, 2012, at 11:18 AM, Andrey Zaytsev wrote: >> >>> Hi! >>> 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 >>> [email protected] >>> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev >> > _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
