search for: fctrl

Displaying 4 results from an estimated 4 matches for "fctrl".

Did you mean: ctrl
2007 Dec 20
4
dotlock errors without using dotlock
I have a few clients that have more than one user in the same mailbox. I have my setup using fctrl for mailbox and index locking. My mail is stored on a network file system (gluster) and my indexes are stored on the local drive. I have a few issues: - My users mailboxes have issues where messages will be mixed up (you go to open a message and it gets a different message) - messages will di...
2010 Nov 25
4
[PATCH]improve suspend_evtchn lock processing
While doing migration, sometimes found suspend lock file was not unlinked in previous operations, then there is an obsolete lock file in place, which causes the current and later migration cannot get lock. That happens seldomly but do happen. After checking the source code, I found there are some places that potentially cause lock file unlinked, including: 1) in lock_suspend_event() function,
2014 Feb 21
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...format:hex;set:General > Purpose Registers;container-regs:e;invalidate-regs:e,23,33,47;#00 > $qRegisterInfo48#ae > $name:r15l;bitsize:8;offset:120;encoding:uint;format:hex;set:General > Purpose Registers;container-regs:f;invalidate-regs:f,24,34,48;#00 > $qRegisterInfo49#af > $name:fctrl;bitsize:16;offset:168;encoding:uint;format:hex;set:Floating > Point Registers;#00 > $qRegisterInfo4a#d7 > $name:fstat;bitsize:16;offset:170;encoding:uint;format:hex;set:Floating > Point Registers;#00 > $qRegisterInfo4b#d8 > $name:ftag;bitsize:8;offset:172;encoding:uint;format:hex;...
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