Displaying 3 results from an estimated 3 matches for "qregisterinfo".
Did you mean:
registerinfo
2014 Feb 21
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...00 Greg Clayton <gclayton at apple.com>:
>
> On Feb 20, 2014, at 1:28 AM, 杨勇勇 <triple.yang at gmail.com> wrote:
>
> > Thank you, Clayton. This is very helpful.
> >
> > We use the LLDB specific GDB remote extensions, and our debugger server
> supports "qRegisterInfo" package. "reg 0x3c" is the frame pointer.
> >
> > In the example mentioned above, we have SP = FP - 40 for current call
> frame.
> > And variable "a" is stored at address (FP + -24) from asm instruction
> [FP + -24] = R3;;
> > Thus we can conc...
2014 Feb 20
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
Thank you, Clayton. This is very helpful.
We use the LLDB specific GDB remote extensions, and our debugger server
supports "qRegisterInfo" package. "reg 0x3c" is the frame pointer.
In the example mentioned above, we have SP = FP - 40 for current call frame.
And variable "a" is stored at address (FP + -24) from asm instruction [FP +
-24] = R3;;
Thus we can conclude that SP + 16 = FP - 40 + 16 = FP -24 is the...
2014 Feb 19
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
Sorry, this is the attachment.
2014-02-19 15:08 GMT+08:00 杨勇勇 <triple.yang at gmail.com>:
> Thank you.
>
> Here is an example and the attchment contains extra files including object
> file and executable file.
> I want to print for example the value of "a", but lldb command "frame
> variable a" displays "0" and so does "b", and