Yeah, only SBExpressionOptions was improved in June 2014, but
SBCompileUnit.GetLanguage() was added very recently in November 2014 (r222189)
and my second question was about that, and it's not yet in the latest Xcode
6.1.1.
> On 27 дек. 2014 г., at 2:33, Jason Molenda wrote:
>
> This change w
This change was around June 2014, it is included in Xcode 6 which was released
around September 2014. The API won't exist in Xcode 5 installations, but I
don't think that's a large number of users.
Yeah we need to figure out how to regenerate the on-line API documentation, I
don't know exactly
Thanks, it works!
And I'm trying to get language based on current frame — it seems that
SBCompileUnit.GetLanguage() was added very recently in r222189. Will it be
added to the Xcode 6 updates?
P.S. Python API reference (http://lldb.llvm.org/python_reference/) is badly
outdated — it says that i
Hi Michail,
Try the SBFrame::EvaluteExpression(const char *expr, const SBExpressionOptions
&options) method where you've specified the language in the SBExpressionOptions
object.
J
> On Dec 24, 2014, at 12:11 AM, Michail Pishchagin wrote:
>
> Hi!
>
> I've been trying to get https://github.
Hi!
I've been trying to get https://github.com/facebook/chisel to work on Swift
targets, and so far noticed one issue: while I'm stopped inside Swift code, all
SBFrame.EvaluateExpression() calls are evaluated as if they're in Swift, not in
Objective-C (this is what Chisel expects).
It's very e
