m2-internship/libunwind-eh_elf
1
0
Fork 0
mirror of https://github.com/tobast/libunwind-eh_elf.git synced 2024-11-26 17:17:39 +01:00
Code Issues Releases Activity

Document that a local unw_resume() across threads results in undefined behavior.

Browse source 
(Logical change 1.59)
This commit is contained in:
mostang.com!davidm 2003-03-06 06:14:36 +00:00
parent eb6d0a751f
commit e2561af01f
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
doc/unw_resume.tex
View file

@ -29,7 +29,10 @@ machine state normally involves restoring the ``preserved''
(callee-saved) registers. However, if execution in any of the stack (callee-saved) registers. However, if execution in any of the stack
frames younger (more deeply nested) than the one identified by frames younger (more deeply nested) than the one identified by
\Var{cursor} was interrupted by a signal, then \Func{unw\_resume}() \Var{cursor} was interrupted by a signal, then \Func{unw\_resume}()
will restore all registers as well as the signal mask. will restore all registers as well as the signal mask. Attempting to
call \Func{unw\_resume}() on a cursor which identifies the stack frame
of another thread results in undefined behavior (e.g., the program may
crash).
For remote unwinding, \Func{unw\_resume}() installs the machine state For remote unwinding, \Func{unw\_resume}() installs the machine state
identified by the cursor by calling the \Func{access\_reg} and identified by the cursor by calling the \Func{access\_reg} and