On 12/05/2017 09:50 PM, Greg Clayton via lldb-dev wrote:
>
>> On Dec 5, 2017, at 12:45 PM, Pedro Alves wrote:
>>
>> On 12/05/2017 06:49 PM, Greg Clayton via lldb-dev wrote:
>>
>>> Though it does seem to be a bug that the "gdbserver" you were using doesn't
>>> support the Target XML packets that
On 12/05/2017 11:17 PM, David Manouchehri wrote:
> Is there a user accessible setting to force on XML target descriptions
> in new-gdbsever?
In gdbserver? Nope.
There's a setting in GDB to force it to not fetch descriptions,
which I found out today didn't actually work. Fixed now in master [1].
On 01/03/2018 07:11 PM, Greg Clayton via lldb-dev wrote:
>
>> On Jan 1, 2018, at 6:30 PM, Owen Shaw via lldb-dev
>> wrote:
>>
>> I dug into this a bit more, and these output reply packets seem to be
>> handled already, but only if the program is running.
>
>> Since the relevant openocd commands
Hi,
Very interesting.
One comment below, about something that jumped at me when
I skimmed the proposal.
On 8/14/19 9:52 PM, Ismail Bennani via lldb-dev wrote:
>
> Since the x86_64 ISA has variable instruction size, LLDB moves enough
> instructions in the trampoline to be able to overwrite them
On 8/22/19 12:36 AM, Ismail Bennani via lldb-dev wrote:
>> On Aug 21, 2019, at 3:48 PM, Pedro Alves wrote:
>> Say, you're using a 5 bytes jmp instruction to jump to the
>> trampoline, so you need to replace 5 bytes at the breakpoint address.
>> But the instruction at the breakpoint address is sho
instructions at the right places
> - now when you debug you have a NOP you can use and not have to worry about
> moving instructions
>
>
>> On Aug 22, 2019, at 5:29 AM, Pedro Alves via lldb-dev
>> wrote:
>>
>> On 8/22/19 12:36 AM, Ismail Bennani via
