[lldb-dev] Fwd: Debugger Futures Meeting notes

[Greg Clayton]

> Begin forwarded message:
> 
> From: Greg Clayton <gclayton at apple.com>
> Subject: Debugger Futures Meeting notes
> Date: October 9, 2014 at 2:48:12 PM PDT
> To: Kate Stone <katherine_stone at apple.com>
> 
> Module Types Feature
> Investigations:
> 1 - do we get any more information for Objective C from modules over what we get from the runtime or debug info?
>    Pros:
>        Do we get full arguments types over what we see in the runtime?
>    Caveats:
>        DWARF debug info should be just as good, but doesn't contain the full definition from a module (can't see private ivars)
> 
> 2 - if we can do better combining ObjC info if the module info isn't complete?
> 
> 3 - ObjC categories that we don't currently handle and figure out how to properly handle them
>    - investigate importing all categories for NSString from a module when we get there and forward when auto importing
> 
> 4 - clang importation of all types. We might need a mode where the compiler wants to also know about:
>    - categories related to importing an ObjC class
>    - properties that might be in categories
>    - if a previous result has a type that conflicts with new types from the current context
>    - when importing straight up RecordDecl, we need them to be upcasted to CXXRecordDecl, this will involve clang work on the importer since we run our expressions in ObjC++...
> 
> 5 - running expression parser in ObjC only mode when possible to avoid differences
>    - Do we never want to access variables from a previous result or anything that already has C++?
> 
> Sean:
> Implement ValueObjectSP ValueObject::Freeze() and use for expression parser and remove ClangExpressionVariable and replace it with ValueObjectConstResult...
> 
> Jim:
> 1 - Expressions throwing objective C exceptions for playgrounds. If the expression is caught by code on stack below expression start frame, then let the exception be thrown. Many bugs on this. 
> - Investigate being able to register EH frame or compact unwind and remove it.
> - Investigate being able to show where the exception would be caught or not caught for any exception thrown during debugging
> 
> 2 - Get value object lists back from complex thread plan ValueObjectSP results for function returns.
> 
> 
> 
>