Searched refs:TCB_STARTUP (Results 1 – 4 of 4) sorted by relevance
1027 tcp->flags |= TCB_ATTACHED | TCB_GRABBED | TCB_STARTUP | in attach_tcb()1061 TCB_STARTUP | post_attach_sigstop; in attach_tcb()1424 tcp->flags |= TCB_ATTACHED | TCB_STARTUP in startup_child()2037 tcp->flags |= TCB_ATTACHED | TCB_STARTUP | post_attach_sigstop; in maybe_allocate_tcb()2166 tcp->flags &= ~TCB_STARTUP; in startup_tcb()2318 if (tcp->flags & TCB_STARTUP) in next_event()
231 #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.
42504 TCB_STARTUP and TCB_IGNORE_ONE_SIGSTOP as two slightly different things.42514 not if TCB_STARTUP is set.42516 Clear TCB_STARTUP and initialize tracee on the very first tracee stop.42523 * strace.c (startup_attach): Use TCB_STARTUP instead of TCB_ATTACH_DONE42528 Set TCB_STARTUP only _after_ we attached.42529 This fixes logic in detach() which thinks that TCB_STARTUP42533 * process.c (internal_fork): Set TCB_STARTUP after attach.42536 (alloc_tcb): Do not set TCB_STARTUP on tcb allocation - we are42538 (trace): Set TCB_STARTUP when we detech an auto-attached child.