summaryrefslogtreecommitdiffhomepage
path: root/src/pty/ntapi_pty_fd.c
AgeCommit message (Collapse)AuthorFilesLines
2018-06-06internals: removed __ntapi_log_write(), as it is no longer needed.midipix1-5/+1
2017-02-04annual chores.midipix1-1/+1
2017-01-26guid <--> string conversion functions: normalized interfaces.midipix1-1/+1
2017-01-07__ntapi_pty_inherit(): do not repeat __ntapi_pty_free() upon failure.midipix1-3/+1
2017-01-07pty interfaces: added __ntapi_pty_open_pair().midipix1-6/+45
2016-08-22pty layer: __ntapi_pty_inherit_runtime_ctty(): implementation and integration.midipix1-0/+109
2016-07-19__ntapi_pty_inherit(): re-set client info, free context upon failure.midipix1-1/+12
2016-07-18pty layer: __ntapi_pty_inherit(): obtain hpty from the server.midipix1-0/+1
2016-07-06__ntapi_pty_open(): properly set the context's hpty member when opening a pts.midipix1-0/+1
2016-06-29__ntapi_pty_open: refactor, explicit string comparison.midipix1-6/+11
2016-05-14__ntapi_pty_connect(): added resilience.midipix1-1/+17
This patch accounts for zw_map_view_of_section() returning NT_STATUS_CONFLICTING_ADDRESSES (0xC0000018) due to third-party software thread creation upon process initialization. The conflict occurs when the address of the stack that is allocated for the third-party thread happens to coincide with the internal section address which was derived from the parent. As should be noted, and while we could decide to always reset ctx->section_addr prior to mapping the internal section, the advantage of the current solution (when acocmpanied by the wrapping calls to __ntapi_log_write) consists in the indication as to whether third-party thread creation had interfered with internal process initialization routines.
2016-01-23annual chores.midipix1-1/+1
2015-09-26pty inheritance: client-side implementation.midipix1-0/+45
2015-07-27entered advanced internal development stage.midipix1-0/+232