Re: [lldb-dev] Setting breakpoint on file and function name doesn't work as expected.

Note first, "break set -f foo.c -l 10" and "break set -f foo.c -n bar" are two very different breakpoints. In the first case, we are looking for a specific file & line combination in the line table or inlined functions info. In the latter case we are searching for a function names bar, and the

Re: [lldb-dev] Slow expression evaluation (ASTImporter is too eager?)

Hi Jaroslav, Thanks for working on this. Still, there are things that are unclear for me. I see that `LayoutRecordType` is called superfluously during the second evaluation of `c2.x`, ok. But, could you explain why LLDB is calling that multiple times? Maybe it thinks a type is not completed while

Re: [lldb-dev] Identifying instructions that definitely access memory

Hi Vangelis, Not sure this will help you, but you can try to compare llvm::MachineInstr::getOpcode() with TargetOpcode::G_LOAD and TargetOpcode::G_STORE if you can obtain a MachineInstr instance. It also may have sense to ask llvm-dev for a proper solution. From: lldb-dev On Behalf Of Vangelis