It looks like you don't have a DynamicLoader plugin that tells lldb where your
binaries ended up in memory when the process ran. The [ADDRESS] means we are
reading instructions from memory not from the on-disk binary.
Jim
> On Jul 9, 2019, at 2:14 AM, Romaric Jodin via lldb-dev
> <lldb-dev@lists.llvm.org> wrote:
>
> HI everyone,
>
> I'm adding my architecture into lldb.
> I'm having some trouble with the debug information on the stack frame.
> LLDB is never displaying any source code. It seems that we I get in
> "StackFrame::GetSymbolContext" "m_flags" is always set to "0xffffffff" but my
> "m_sc" does not contains the information needed about the module
> ("module_sp=0x0").
> But LLDB can read the elf file and find information like here:
>
> Process 21312 stopped
> * thread #1, name = 'DPUthread0', stop reason = suspended
> frame #0: 0x80000018
> test`__bootstrap:
> test[0x80000018] <+24>: sub r0, r0, 0x1, pl, 0x80000010
> test[0x80000020] <+32>: jgeu id, 0x3, 0x80000058
> test[0x80000028] <+40>: jeq id, 0x2, 0x80000038
> test[0x80000030] <+48>: boot id, 0x1
>
> or here:
>
> (lldb) b main
> Breakpoint 1: where = test`main + 32 at test.c:29, address = 0x80000080
>
> Do someone get what I'm missing?
>
> Thanks,
> --
> Romaric JODIN
> UPMEM
> Software Engineer
>
> <logo signature mail 50x50.png>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
_______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
