Searched refs:TCB_STARTUP (Results 1 – 4 of 4) sorted by relevance
1036 tcp->flags |= TCB_ATTACHED | TCB_STARTUP | post_attach_sigstop; in attach_tcb()1070 tid_tcp->flags |= TCB_ATTACHED | TCB_STARTUP | in attach_tcb()1433 tcp->flags |= TCB_ATTACHED | TCB_STARTUP in startup_child()2045 tcp->flags |= TCB_ATTACHED | TCB_STARTUP | post_attach_sigstop; in maybe_allocate_tcb()2171 tcp->flags &= ~TCB_STARTUP; in startup_tcb()2365 if (tcp->flags & TCB_STARTUP) { in trace()
246 #define TCB_STARTUP 0x01 macro
202 tcb has TCB_STARTUP bit set - we can attach to the task1305 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.
30876 TCB_STARTUP and TCB_IGNORE_ONE_SIGSTOP as two slightly different things.30886 not if TCB_STARTUP is set.30888 Clear TCB_STARTUP and initialize tracee on the very first tracee stop.30895 * strace.c (startup_attach): Use TCB_STARTUP instead of TCB_ATTACH_DONE30900 Set TCB_STARTUP only _after_ we attached.30901 This fixes logic in detach() which thinks that TCB_STARTUP30905 * process.c (internal_fork): Set TCB_STARTUP after attach.30908 (alloc_tcb): Do not set TCB_STARTUP on tcb allocation - we are30910 (trace): Set TCB_STARTUP when we detech an auto-attached child.