Lines Matching refs:error
7 The errors are put on the error stack (rather a queue but error stack is
10 error return value. The `SSL_get_error()` call depends on the stack being
12 call caused a library or system (I/O) error.
14 The error stacks are thread-local. Libssl API calls from separate threads
15 push errors to these separate error stacks. It is unusual to invoke libssl
29 The error stack access is not under a lock (because it is thread-local).
38 This document assumes the actual error state of the QUIC connection (or stream
39 for stream level errors) is handled separately from the auxiliary error reason
40 entries on the error stack.
43 to the error stack.
47 type is an intermittent error that does not really affect the state of the
50 is a permanent error that affects the error state of the QUIC connection.
53 QUIC connection to enter an error state, or if they just affect the stream
54 they are left on the error stack of the thread that called SSL_write()
61 depend on the error stack contents.
64 error stack before returning to the user.
73 There is an error stack in QUIC_CHANNEL which serves as temporary storage
74 for errors happening in the internal assistance thread. When a permanent error
75 is detected the error stack entries are moved to this error stack in
79 a permanent connection error, entries from the QUIC_CHANNEL error stack
80 are copied to the thread local error stack. They are always kept on
81 the QUIC_CHANNEL error stack as well for possible further calls from
82 an application. An additional error reason
89 a permanent error on the connection. The only case when SSL_tick() may
90 return an error is when there was some fatal error processing it
91 such as a memory allocation error where no further SSL_tick() calls
98 multi-stream-multi-thread mode as the error stack entries are always
101 the same error stack entries to report to the user.
