Ah, that’s right, we did it in debugserver as well. Apple used to have a
disassembly framework that we used for the purpose (separate from llvm). But
that’s long gone.
Jim
> On Nov 29, 2018, at 1:22 AM, Pavel Labath wrote:
>
> On 28/11/2018 21:05, Jim Ingham via lldb-dev wrote:
>> The main
On 28/11/2018 21:05, Jim Ingham via lldb-dev wrote:
The main complication would be if your new target didn't support
hardware-single-step. If that's the case you will have to have a Disassembler
that can predict the target PC of all instructions (when stopped at that
instruction) since you'll
You will need to add ABI support. You'll also need to make an Unwinder that
works for your platform. But the thread plan code is pretty generic and relies
on the Unwinder and generic features of the Disassembler (mostly "IsBranch") to
do its job. For instance, thread step-out just asks the Un
Hi Everyone,
I’ve added basic support for a new target (via gdb-remote) and now it is time
to add ABI support to lldb to improve the debug experience. My understanding is
that I need to add an ABI plugin (we have a very basic stub now) and
thread-plan support. As a first step I’d like to be abl
