We've ran into the same issue when we were adding the "dynamic
register size" fields, which is mips thing. I think we need a more
flexible way of specifying the register context structs (constexpr
constructors?) which will not suffer from these issues.
On 14 July 2017 at 16:39, Tatyana Krasnukha
y, 13 July, 2017 3:01 PM
To: 'Pavel Labath'
Cc: lldb-dev@lists.llvm.org
Subject: RE: [lldb-dev] Skipping registers when restore register state after a
function call
Yes, you are right about bug in the stub, and that returning of an error will
not solve the problem. I like the id
ndesirable behavior.
Thanks,
Tatyana
-Original Message-
From: Pavel Labath [mailto:lab...@google.com]
Sent: Thursday, 13 July, 2017 2:37 PM
To: Tatyana Krasnukha
Cc: lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] Skipping registers when restore register state after a
function call
Aha, I s
attempt to
> write some registers that shouldn't be written.
>
> Thanks,
> Tatyana
>
> -Original Message-
> From: Pavel Labath [mailto:lab...@google.com]
> Sent: Thursday, 13 July, 2017 2:16 PM
> To: Tatyana Krasnukha
> Cc: lldb-dev@lists.llvm.org
> Su
s,
Tatyana
-Original Message-
From: Pavel Labath [mailto:lab...@google.com]
Sent: Thursday, 13 July, 2017 2:16 PM
To: Tatyana Krasnukha
Cc: lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] Skipping registers when restore register state after a
function call
I'm not sure there is a good
I'm not sure there is a good way to do that currently.
However, if you tell us what is the higher level problem you are
trying to solve, we may be able to provide an alternative (right now,
the only reason I can think of why you would *not* want to
save/restore all registers is the orig_rax pseudo
Hi,
I need an ability to skip some registers when lldb restores register state
after a function call. Didn't find something like gdb "save-restore" register
property. Is there any way to avoid restoring of some registers beside
hardcoding its names in GDBRemoteRegisterContext::WriteAllRegisterVa