Lines Matching refs:shadow

30 I have a shadow call stack for every thread. For signal handlers of a thread, 
31 I first PUSH a separation marker on the shadow stack, and use the stack as 
45 - do unwinding if needed (i.e, POPs of the shadow call stack)
55   BB on shadow call stack.
59 as we need separate shadow call stacks.
114 > - have a shadow call stack for every thread
123 changes with %esp > stored esp on shadow stack.
142 > - Unwind the shadow call stack if necessary.
143 > [when is "necessary"?  If the real %esp > the shadow stack %esp?]
149 > - If this is a function return and there was no shadow stack unwinding,
151 > linker).  Pop the shadow call stack, setting the previous BB address to
158 function) at least one entry of the shadow call stack. But this doesn't need 
160 one on the shadow stack. E.g. suppose
173 > from previous BB to current BB on shadow call stack.
176 I meant: Append a struct call_entry to the shadow stack (together with the 
177 current %esp value). As I said before, the shadow stack is used for robust 
186 > thread's shadow stack, then use it as normal.  The marker is used for
191 > handlers, as we need separate shadow call stacks.
192 > [Do you mean "separate shadow call stacks for each thread"?]