Re: [lldb-dev] Symbolic information in disassembler output

2017-08-31 Thread Tatyana Krasnukha via lldb-dev
ugust, 2017 9:35 PM To: lldb-dev@lists.llvm.org Subject: Re: [lldb-dev] Symbolic information in disassembler output Greg is right that this was a libedis feature and has no equivalent in LLDB today. MCInst, however, doesn't have enough information by itself to do this. The reason is tha

Re: [lldb-dev] Symbolic information in disassembler output

2017-08-31 Thread Sean Callanan via lldb-dev
Greg is right that this was a libedis feature and has no equivalent in LLDB today. MCInst, however, doesn't have enough information by itself to do this.  The reason is that for many things that are considered "operands," the MCInst has several underlying operands.  For example, an operand tha

Re: [lldb-dev] Symbolic information in disassembler output

2017-08-31 Thread Greg Clayton via lldb-dev
I believe libedis was deprecated many years ago and hasn't returned. We use the standard LLVM disassembler, so any features need to be built into llvm::MCInst. > On Aug 31, 2017, at 10:42 AM, Tatyana Krasnukha via lldb-dev > wrote: > > Hello, > > As I understand it, old disassembler (based

Re: [lldb-dev] Symbolic information in disassembler output

2017-08-31 Thread Jim Ingham via lldb-dev
I don't think anybody thought of it as useless. It's one of the things Jason has been trying to find time to do for a while now. InstructionLLVMC is the main concrete Instruction subclass in llvm now, and relies on MCInst for most of the heavy lifting. So we should work with MCInst to figure

[lldb-dev] Symbolic information in disassembler output

2017-08-31 Thread Tatyana Krasnukha via lldb-dev
Hello, As I understand it, old disassembler (based on libedis) could print symbolic information instead/beside address operand of an instruction. And it looks like there is not such ability in disassembler now. Is this responsibility shifted on some other component of lldb? Or it was considered