search for: disassemblerllvmc

...ebug and check what is going on. > > > > There is the possibility to be lldb usage, but it’s obtaining the > disassembler as it is. > > When lldb tries to instantiate the disassembler, it checks many > information in > > llvm/tools/lldb/source/Plugins/Disassembler/llvm/DisassemblerLLVMC.cpp:1014 > = > > “DisassemblerLLVMC::DisassemblerLLVMC(const ArchSpec &arch, const char > *flavor_string)”, > > which I couldn’t find if it’s doing correct. Is there a place that > explains the “flavor” and > > “features_str” variables used at DisassemblerLLVMC.cpp:11...

...; > > > is not working for some cases. > > > > > > > > When debugging, I can see that the disassembler analyze some instructions > > > > forward, looking for a branch instruction > > > > (llvm/tools/lldb/source/Plugins/Disassembler/llvm/ > DisassemblerLLVMC.cpp:87 > > > > – “const bool can_branch = mc_disasm_ptr->CanBranch(inst);”), while > > > > trying to set the next breakpoint. > > > > > > > > On this case, the instruction is the “bne cr7,0x2000092c”, which is a > > branch, > > >...

Hi all, I'm working on lldb to make it available to ppc64le, but the "step over" is not working for some cases. When debugging, I can see that the disassembler analyze some instructions forward, looking for a branch instruction (llvm/tools/lldb/source/Plugins/Disassembler/llvm/DisassemblerLLVMC.cpp:87 - "const bool can_branch = mc_disasm_ptr->CanBranch(inst);"), while trying to set the next breakpoint. On this case, the instruction is the "bne cr7,0x2000092c", which is a branch, but at llvm/lib/MC/MCInstrDesc.cpp:35 - "if (isBranch() || isCall() || isRetur...