Re: [lldb-dev] ThreadPlanStepOverBreakpoint behavior

Sorry for the delay, I revisited the issue today. It is causing a problem for our architecture which does not support single instruction stepping. We emulate it with breakpoints and a processor exception on branch taken. For example: When we step over a line with a breakpoint, our flavor of St

[lldb-dev] [BUG] Many lookup failures

Hi, Basic things are failing. (lldb) p lhs (CG::VarExpr *) $0 = 0x00010d445ca0 (lldb) p lhs->rootStmt() (CG::ExprStmt *) $1 = 0x00010d446290 (lldb) p cg_pp_see_it(lhs->rootStmt()) (const char *) $2 = 0x00010d448020 "%A = $3;" (lldb) p cg_pp_see_it(def->rootStmt()) error: no member nam

Re: [lldb-dev] Linux core dump doesn't show listing when loaded

There has been some discussion in , as to what get's printed when, but I don't think any changes went in yet. I wouldn't be opposed to bringing back the old behavior (or keeping the current one, for that matter), but I feel that any change here should consistent with

[lldb-dev] [Bug 25632] New: LLDB does not use the .debug_frame section to read the CFI

https://llvm.org/bugs/show_bug.cgi?id=25632 Bug ID: 25632 Summary: LLDB does not use the .debug_frame section to read the CFI Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW

Re: [lldb-dev] Inquiry about .debug_frame

Yes sure. On Wed, Nov 25, 2015 at 8:00 AM, wrote: > lldb should be able to read both. Can you file a bug please? > On Tue, Nov 24, 2015 at 02:50:20PM +0100, Ravitheja Addepally via lldb-dev > wrote: > > Hello, > >While compiling with clang for i386, I notice that the CFI > > information