/barrelfish-2018-10-04/lib/openssl-1.0.0d/util/ |
H A D | pod2mantest | 32 failure=none 37 failure=BasicTest 40 if [ "$failure" = none ]; then 42 failure=MultilineTest 47 if [ "$failure" = none ]; then 52 echo "$pod2man does not work properly ('$failure' failed). Looking for another pod2man ..." >&2
|
/barrelfish-2018-10-04/lib/openssl-1.0.0d/test/ |
H A D | bctest | 31 failure=none 51 failure=SunOStest 55 if [ "$failure" = none ]; then 86 failure=SCOtest 91 if [ "$failure" = none ]; then 102 echo "$bc does not work properly ('$failure' failed). Looking for another bc ..." >&2
|
H A D | bctest.com | 8 $ failure = "" 18 $ if (failure .eqs. "") 41 $ failure = "SunOStest" 49 $ if (failure .eqs. "") 84 $ failure = "SCOtest" 92 $ if (failure .eqs. "") 103 $ failure = "printtest" 109 $ if (failure .nes. "") 119 $! Complete "bc" command failure.
|
/barrelfish-2018-10-04/lib/libc/rpc/ |
H A D | rpcb_st_xdr.c | 63 if (!xdr_int(xdrs, &objp->failure)) { 104 if (!xdr_int(xdrs, &objp->failure)) { 115 IXDR_PUT_INT32(buf, objp->failure); 143 if (!xdr_int(xdrs, &objp->failure)) { 154 objp->failure = (int)IXDR_GET_INT32(buf); 179 if (!xdr_int(xdrs, &objp->failure)) {
|
/barrelfish-2018-10-04/lib/cxx/cxx/ |
H A D | ios.cpp | 74 // ios_base::failure 76 ios_base::failure::failure(const string& msg, const error_code& ec) function in class:ios_base::failure 81 ios_base::failure::failure(const char* msg, const error_code& ec) function in class:ios_base::failure 86 ios_base::failure::~failure() throw() 276 throw failure("ios_base::clear");
|
/barrelfish-2018-10-04/lib/compiler-rt/builtins/ |
H A D | atomic.c | 194 void *desired, int success, int failure) { 197 *(type*)desired, success, failure) 284 int success, int failure) {\ 287 success, failure);\ 193 __atomic_compare_exchange_c(int size, void *ptr, void *expected, void *desired, int success, int failure) argument
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/megalog/ |
H A D | multiuser-sec.tex | 268 a system failure 269 \footnote{A `system failure' is when there is a hardware or software 270 failure that requires a process(es) to be restarted, but does not affect secondary storage.}. 271 If system failure occurs while \eclipse is executing transactions a 273 a failure the database will be left in a consistent state, 287 Recovery after a system failure is also provided in single user \eclipse. 290 Note that recovery from system failure is only guaranteed to work if
|
/barrelfish-2018-10-04/lib/mdb/ |
H A D | mdb_tree.c | 40 // on failure, dump mdb and terminate 43 mdb_dump_and_fail(struct cte *cte, enum mdb_invariant failure) argument 46 panic("failed on cte %p with failure %s (%d)\n", 47 cte, mdb_invariant_to_str(failure), failure); 49 #define MDB_RET_INVARIANT(cte, failure) mdb_dump_and_fail(cte, failure) 51 #define MDB_RET_INVARIANT(cte, failure) return failure
|
/barrelfish-2018-10-04/doc/016-serial-ports/ |
H A D | Serial.tex | 111 and doing so will cause an assertion failure. 124 assertion failure. It may also cause an assertion failure to call
|
/barrelfish-2018-10-04/usr/eclipseclp/Kernel/lib/ |
H A D | notinstance.pl | 199 T0 = T % one step closer to failure ... 208 T0 = T. % one step closer to failure ...
|
H A D | tracer.pl | 149 % Redo notification handler, called after the failure happened. 150 % Stack: the current (restored) stack after the failure 152 % RedoLevel: at which level the failure was caught, ie the youngest
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/internal/kernel/ |
H A D | debugger.tex | 86 On failure, the ancestor stack is popped (since it is a logical data 89 survives failure. The arguments are lost. Depth is implicit and 111 Tracing exit_block/leave ports is done like failure tracing. 318 Simple tests are often executed with a shallow choicepoint, i.e. failure
|
/barrelfish-2018-10-04/usr/eclipseclp/Opium/demo/ |
H A D | yoyo2.pl | 19 BUGGY: endless loop (failure-driven endless recursion). \n').
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/userman/ |
H A D | umscmdlineopts.tex | 61 The exit status of the {\eclipse} process reflects success or failure of the 63 executed Prolog goal (0 for success, 1 for failure, 2 for abort).
|
H A D | umsstyle.tex | 77 \item The final code should not use failure-loops\index{failure loop}; they are
|
H A D | umsmemory.tex | 232 It is popped only on failure. {\eclipse} therefore provides a garbage collector 251 The Trail Stack is popped on failure and
|
H A D | umsstring.tex | 57 the space is reclaimed on failure and on garbage collection.
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/libman/ |
H A D | eplexdiff.tex | 86 will lead to failure, i.e.\ if the upper bound of a variable becomes 87 smaller than its lower bound, this will result in failure, either 115 is called, then failure will occur if the bounds are inconsistent between
|
H A D | extconjunto.tex | 139 set variables. A failure is detected in the constraint propagation 516 be deduced from a failure (backtrack) whereas if (like in the refine 518 ground or some failure is detected, we benefit much more from the 523 either the goal succeeds or it fails. In case of failure the labeling
|
/barrelfish-2018-10-04/usr/eclipseclp/Opium/ |
H A D | loadopium.pl | 153 make(failure, abstracts, UntrGlobal, SD, OD),
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/embedding/ |
H A D | embfunc.tex | 47 failure. Note however, that if attributed variables are
|
/barrelfish-2018-10-04/lib/openssl-1.0.0d/crypto/ts/ |
H A D | ts_rsp_sign.c | 386 int TS_RESP_CTX_add_failure_info(TS_RESP_CTX *ctx, int failure) argument 391 if (!ASN1_BIT_STRING_set_bit(si->failure_info, failure, 1))
|
H A D | ts.h | 493 Return non-zero for success and zero for failure. */ 499 * status info/failure info of the response). 595 int TS_RESP_CTX_add_failure_info(TS_RESP_CTX *ctx, int failure);
|
/barrelfish-2018-10-04/include/openssl/ |
H A D | ts.h | 493 Return non-zero for success and zero for failure. */ 499 * status info/failure info of the response). 595 int TS_RESP_CTX_add_failure_info(TS_RESP_CTX *ctx, int failure);
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/tutorial/ |
H A D | tkdebug.tex | 226 an exit port. Red (failure) for a fail port. Note that in the call 599 \item[Analyse failure] Get the invocation number of the most recent failure
|