search for: fiseg

Displaying 2 results from an estimated 2 matches for "fiseg".

Did you mean: iseg
2014 Feb 21
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...gisters;#00 > $qRegisterInfo4c#d9 > $name:fop;bitsize:16;offset:173;encoding:uint;format:hex;set:Floating > Point Registers;#00 > $qRegisterInfo4d#da > $name:fioff;bitsize:32;offset:175;encoding:uint;format:hex;set:Floating > Point Registers;#00 > $qRegisterInfo4e#db > $name:fiseg;bitsize:16;offset:179;encoding:uint;format:hex;set:Floating > Point Registers;#00 > $qRegisterInfo4f#dc > $name:fooff;bitsize:32;offset:181;encoding:uint;format:hex;set:Floating > Point Registers;#00 > $qRegisterInfo50#a7 > $name:foseg;bitsize:16;offset:185;encoding:uint;format:he...
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