Using lldb 300.99.0 with Xcode 4.6.2?

Is there any way to update/upgrade the lldb that Xcode uses to the latest version?

Thanks in advance - AYAL

Ayal Spitz | Senior Software Engineer, Mobile | PatientKeeper

No, there has been at least one change to the lldb APIs since Xcode 4.6 was released which make them binary incompatible.

Any chance this will change in the future?

Thanks - AYAL

Ayal Spitz | Senior Software Engineer, Mobile | PatientKeeper

As we solidify our API this will happen less in the future.

We haven't yet said that we have API version 1.0 yet, so we haven't locked down on any API as it needed to be able to change as we evolved LLDB.

Got it. Thanks so much - AYAL

Ayal Spitz | Senior Software Engineer, Mobile | PatientKeeper

I actually just checked and top of tree LLDB can be used with Xcode 4.6.2. No APIs have changed that Xcode requires.

I have a script that can do API verification. It is checked into the LLDB tree (lldb/scripts/verify_api.py) which can be used to verify. If you have a LLDB.framework in the current working directory you can run:

lldb/scripts/verify_api.py --library ./LLDB.framework/LLDB --arch x86_64 /Applications/Xcode.app/Contents/PlugIns/DebuggerLLDB.ideplugin/Contents/MacOS/DebuggerLLDB --api-regex lldb

It shows that all necessary calls required by the installed "DebuggerLLDB.ideplugin" in Xcode are present.

To try out the latest LLDB, build a release version of the LLDB.framework and then point Xcode to the version you just built _without_ installing it by quitting Xcode and then running the following in the terminal:

cd build/Release
DYLD_FRAMEWORK_PATH=`pwd` /Applications/Xcode.app/Contents/MacOS/Xcode

This will cause Xcode to run using the LLDB.framework from the current working directory.

You will need to follow the code signing docs in lldb/docs/code-signing.txt to make your own code signing certificate.

Greg

Excellent!! Thank you very much - AYAL

Ayal Spitz | Senior Software Engineer, Mobile | PatientKeeper