On Apr 29, 2020, at 9:28 PM, Rui Hong
mailto:hongru...@mails.ucas.ac.cn>> wrote:
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!
You’re welcome!
*4. by the way, does GDB has similar
at
it. Most people will run fully linked executables (these tend to have PT_LOAD
segments) when they run on a simuilator, not an unlinked object file (these
tend to not have PT_LOAD segments). It shouldn't be too hard to get a
statically linked executable with the right ELF program headers (P
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
> On Apr 16, 2020, at 2:30 AM, Rui Hong via lldb-dev
> wrote:
>
> 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 comm
Hi Rui,
What you describe is almost identical to what we do with the Hexagon simulator.
There are 2 ways to launch your program - “run” (process launch) and gdb-remote
(an attach).
“run” will require some plumbing to launch your simulator the same way that
lldb-server/debugserver is launched.
