Hi LLDB devs,
I'm working on porting LLDB to my own architecture.
I choose to use the target-definition-file(python) to let LLDB support my
architecture based on my situation(already have a workable GDB-stub and the
target is an embedded DSP). The usage:
(lldb) settings set plugin.process.gdb-r
Hi LLDB devs,
First I want to thank you all for the very helpful advice on my former
question! It's a really nice community.
I have a small problem now about LLDB tab completion and I haven't found any
solutions so far. I used to have nice tab completion before. But I cannot get
this feature
Hi LLDB devs,
I'm working on porting LLDB to work with an existing simulator(which has GDB
stub, remote debugging). This simulator used to work with GDB. When using with
GDB, the target file(ELF) is loaded by GDB command "load" or "remote put".
From a LLVM talk project which is very similar to m
Hi LLDB devs,
First I would like to express my appreciation and thanks to you all especially
Greg Clayton and Ted Woodward! Your advice and guidance are quite useful for me!
I've been working on other lldb problems and resume solving the "remote
loading" issue now. I now fully understand the
Hi LLDB devs,
I have almost finished porting LLDB to my architecture, now LLDB communicates
well with my GDB stub of my simulator and can do debugging actions like
breakpoint, continue, step, reading memory, reading registers and so on. Thanks
to all of your kind advice~
Now I consider addin