Home
last modified time | relevance | path

Searched refs:TCB_STARTUP (Results 1 – 4 of 4) sorted by relevance

/external/strace/
Dstrace.c719 tcp->flags |= TCB_ATTACHED | TCB_STARTUP | flags; in after_successful_attach()
2184 tcp->flags &= ~TCB_STARTUP; in startup_tcb()
2381 if (tcp->flags & TCB_STARTUP) in next_event()
Ddefs.h251 #define TCB_STARTUP 0x01 macro
DChangeLog-CVS202 tcb has TCB_STARTUP bit set - we can attach to the task
1305 new SIGSTOP for processes still in TCB_STARTUP.
1308 have been already caught before clearing TCB_STARTUP.
1310 Clear TCB_STARTUP only in the case the received signal was SIGSTOP.
1311 New comment when `TCB_BPTSET && TCB_STARTUP' combination can be set.
DChangeLog4971 Set TCB_ATTACHED, TCB_STARTUP, and "flags" in tcp->flags.
50066 TCB_STARTUP and TCB_IGNORE_ONE_SIGSTOP as two slightly different things.
50076 not if TCB_STARTUP is set.
50078 Clear TCB_STARTUP and initialize tracee on the very first tracee stop.
50085 * strace.c (startup_attach): Use TCB_STARTUP instead of TCB_ATTACH_DONE
50090 Set TCB_STARTUP only _after_ we attached.
50091 This fixes logic in detach() which thinks that TCB_STARTUP
50095 * process.c (internal_fork): Set TCB_STARTUP after attach.
50098 (alloc_tcb): Do not set TCB_STARTUP on tcb allocation - we are
50100 (trace): Set TCB_STARTUP when we detech an auto-attached child.