It is quite strange that the problem is occurring to you even using the latest
LLDB. I tried to stick exactly to what you had typed: "expr [item title]", and
still I do not get a crash:
(lldb) expr [item title]
(NSString *) $1 = 0x0000000100001238
Moreover, while I have not really had a chance to debug the debugger's
evaluation of your expression, the code snippet that you pinpoint as the
culprit (dereferencing a NULL pointer in GetCompleteQualType()), is fixed now:
case clang::Type::ObjCObject:
case clang::Type::ObjCInterface:
{
const clang::ObjCObjectType *objc_class_type =
dyn_cast<clang::ObjCObjectType>(qual_type);
if (objc_class_type)
{
clang::ObjCInterfaceDecl *class_interface_decl =
objc_class_type->getInterface();
// We currently can't complete objective C types through the
newly added ASTContext
// because it only supports TagDecl objects right now...
if(class_interface_decl)
{
bool is_forward_decl =
class_interface_decl->isForwardDecl(); <-- only do it if class_interface_decl
is not NULL
You might want to make sure you have grabbed the recent-most LLDB source code
from the SVN repository. And, if this still not helps, probably sharing your
source code so others can experiment with it and check exactly what is going
wrong might be a good idea :).
Thanks again for your interest in LLDB.
On Jul 14, 2011, at 10:30 AM, Andrey Zaytsev wrote:
>
> On 14.07.2011, at 20:09, Enrico Granata wrote:
>
>> Andrey,
>> You might be pleased to know that this bug is fixed in the latest LLDB
>
> Hi, Enrico!
> Thank you for consideration of my problem.
> But your listing doesn't show described problem because "expr (char*)[[itm
> title] UTF8String]" doesn't invoke GetNumChildren method of SBValue. But if
> you do it (e.g. from python script) you'll get the crash.
> It's reproduced with latest sources. (tried right now)
>
> Fixing this problem will make this feature work:
>
> <Screen shot 2011-07-14 at 21.27.13.png>
>
> Xcode have the similar one in the variables view. But it doesn't work. And if
> Xcode team will fix that issue with "Invalid expression" they will face the
> described one =(
> Thank you for consideration.
>
>
>
> _______________________________________________
> 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
