http://llvm.org/bugs/show_bug.cgi?id=17226
Bug ID: 17226
Summary: frame info lost after failed expression evaluation
Product: lldb
Version: unspecified
Hardware: PC
OS: FreeBSD
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: [email protected]
Reporter: [email protected]
Classification: Unclassified
Encountered while investigating TestObjCStepping.test_with_dwarf_and_python_api
% bin/lldb ../tools/lldb/test/lang/c/stepping/a.out
Current executable set to '../tools/lldb/test/lang/c/stepping/a.out' (x86_64).
(lldb) b 34
Breakpoint 1: where = a.out`b + 11 at main.c:34, address = 0x000000000040064b
(lldb) run
Process 70433 launched: '../tools/lldb/test/lang/c/stepping/a.out' (x86_64)
Process 70433 stopped
* thread #1: tid = 70433, 0x000000000080064b a.out`b(val=1) + 11 at main.c:34,
stop reason = breakpoint 1.1
frame #0: 0x000000000080064b a.out`b(val=1) + 11 at main.c:34
31
32 int b(int val)
33 {
-> 34 int rc = c(val); // thread step-out while stopped at "c(2)"
35 return rc;
36 }
37
(lldb) expr (int) printf (print_string)
error: Couldn't materialize struct: size of variable print_string disagrees
with the ValueObject's size
Errored out in Execute, couldn't PrepareToExecuteJITExpression
(lldb) frame info
frame #0: 0x00000000008004d0 a.out`_start(ap=0x0000000000000000,
cleanup=0x0000000000001000) at crt1.c:65
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
