/barrelfish-2018-10-04/usr/eclipseclp/Visualisation/src/com/parctechnologies/eclipse/visualisation/ |
H A D | VisException.java | 38 public VisException(String message) argument 40 super(message);
|
H A D | DebuggingSupport.java | 31 public static void logMessage(Object obj, Object message) argument 35 System.err.println(message);
|
/barrelfish-2018-10-04/include/lwip2/lwip/ |
H A D | debug.h | 71 /** flag for LWIP_DEBUGF to enable that debug message */ 73 /** flag for LWIP_DEBUGF to disable that debug message */ 79 /** @name Debug message types (LWIP_DBG_TYPES_ON) 82 /** flag for LWIP_DEBUGF indicating a tracing message (to follow program flow) */ 84 /** flag for LWIP_DEBUGF indicating a state debug message (to follow module states) */ 88 /** flag for LWIP_DEBUGF to halt after printing this debug message */ 116 #define LWIP_ASSERT(message, assertion) do { if (!(assertion)) { \ 117 LWIP_PLATFORM_ASSERT(message); }} while(0) 119 #error "If you want to use LWIP_ASSERT, LWIP_PLATFORM_ASSERT(message) needs to be defined in your arch/cc.h" 122 #define LWIP_ASSERT(message, assertio [all...] |
/barrelfish-2018-10-04/include/lwip/lwip/ |
H A D | debug.h | 49 /** flag for LWIP_DEBUGF to enable that debug message */ 51 /** flag for LWIP_DEBUGF to disable that debug message */ 54 /** flag for LWIP_DEBUGF indicating a tracing message (to follow program flow) */ 56 /** flag for LWIP_DEBUGF indicating a state debug message (to follow module states) */ 60 /** flag for LWIP_DEBUGF to halt after printing this debug message */ 64 #define LWIP_ASSERT(message, assertion) do { if(!(assertion)) \ 65 LWIP_PLATFORM_ASSERT(message); } while(0) 67 #define LWIP_ASSERT(message, assertion) 70 /** if "expression" isn't true, then print "message" and execute "handler" expression */ 72 #define LWIP_ERROR(message, expressio [all...] |
/barrelfish-2018-10-04/tools/harness/ |
H A D | debug.py | 19 def message(level, message): function 21 sys.stdout.write(message + '\n') 25 message(QUIET, 'Warning: ' + s) 28 message(QUIET, 'Error: ' + s) 31 message(NORMAL, s) 34 message(VERBOSE, s) 37 message(DEBUG, s) 43 # display verbose message saying what we do
|
H A D | checkout.py | 96 ret["commitmsg"] = headc.message.split("\n")[0] 97 ret["commitmsg-tail"] = "".join(headc.message.split("\n")[1:])
|
/barrelfish-2018-10-04/usr/eclipseclp/Opium/ |
H A D | opium-mode.el | 58 (message "opium_scenario defined")) 101 (message "opium_command defined")) 132 (message "opium_primitive defined")) 159 (message "opium_procedure defined")) 194 (message "opium_parameter defined")) 213 (message "opium_type defined")) 236 (message "opium_demo defined"))
|
/barrelfish-2018-10-04/lib/cxx/cxx/ |
H A D | system_error.cpp | 46 __do_message::message(int ev) const function in class:__do_message 56 virtual string message(int ev) const; 66 __generic_error_category::message(int ev) const function in class:__generic_error_category 75 return __do_message::message(ev); 90 virtual string message(int ev) const; 101 __system_error_category::message(int ev) const function in class:__system_error_category 110 return __do_message::message(ev); 136 error_condition::message() const function in class:error_condition 138 return __cat_->message(__val_); 144 error_code::message() cons function in class:error_code [all...] |
/barrelfish-2018-10-04/lib/lwip2/src/netif/ppp/ |
H A D | chap-md5.c | 64 char *message, int message_space) { 86 ppp_slprintf(message, message_space, "Access granted"); 90 ppp_slprintf(message, message_space, "Access denied"); 61 chap_md5_verify_response(ppp_pcb *pcb, int id, const char *name, const unsigned char *secret, int secret_len, const unsigned char *challenge, const unsigned char *response, char *message, int message_space) argument
|
H A D | chap-new.c | 57 char *message, int message_space) = NULL; 98 char *message, int message_space); 294 char message[256]; local 330 response, pcb->chap_server.message, sizeof(pcb->chap_server.message)); 334 response, message, sizeof(message)); 346 mlen = strlen(message); 364 memcpy(outp + CHAP_HDRLEN, message, mlen); 414 char *message, in 411 chap_verify_response(ppp_pcb *pcb, const char *name, const char *ourname, int id, const struct chap_digest_type *digest, const unsigned char *challenge, const unsigned char *response, char *message, int message_space) argument [all...] |
/barrelfish-2018-10-04/include/lwip2/netif/ppp/ |
H A D | chap-md5.c | 64 char *message, int message_space) { 86 ppp_slprintf(message, message_space, "Access granted"); 90 ppp_slprintf(message, message_space, "Access denied"); 61 chap_md5_verify_response(ppp_pcb *pcb, int id, const char *name, const unsigned char *secret, int secret_len, const unsigned char *challenge, const unsigned char *response, char *message, int message_space) argument
|
H A D | chap-new.h | 139 char *message, int message_space); 177 char *message, int message_space);
|
H A D | chap-new.c | 57 char *message, int message_space) = NULL; 98 char *message, int message_space); 294 char message[256]; local 330 response, pcb->chap_server.message, sizeof(pcb->chap_server.message)); 334 response, message, sizeof(message)); 346 mlen = strlen(message); 364 memcpy(outp + CHAP_HDRLEN, message, mlen); 414 char *message, in 411 chap_verify_response(ppp_pcb *pcb, const char *name, const char *ourname, int id, const struct chap_digest_type *digest, const unsigned char *challenge, const unsigned char *response, char *message, int message_space) argument [all...] |
/barrelfish-2018-10-04/lib/compiler-rt/builtins/ |
H A D | int_util.c | 38 const char *message);
|
/barrelfish-2018-10-04/include/ |
H A D | arranet_debug.h | 78 } message; member in union:__anon37 88 } message; member in union:__anon39
|
/barrelfish-2018-10-04/tools/ |
H A D | mkefi.py | 27 message = _("not a file '%s'")
|
/barrelfish-2018-10-04/doc/006-routing/ |
H A D | Routing.tex | 39 implementation) of multi-hop message routing in Barrelfish -- how to 69 such environments, without having to worry about the concrete path a message takes from one core to another. The routing layer will properly route messages in a transparent way. 116 The sender sends the message to a subset of nodes it wishes to communicate with. 150 Interconnect drivers in Barrelfish generally provide a reliable messaging service: A message is delivered only once and each message sent is eventually delivered and its content is not corrupted. Furthermore, messages are delivered in FIFO order. The multi-hop interconnect driver is designed to provide a reliable messaging service in principle. However, contrary to the end-to-end argument, it does not provide any \emph{end-to-end} reliability, but builds on the reliability provided by the interconnect drivers of the underlying links. We accept that the multi-hop interconnect driver can fail in case any of the interconnect drivers of the underlying link fail. 177 Those additional channels are needed to ensure that the default monitor binding is not congested or even blocked by multi-hop messages. For example, suppose that a client's dispatcher receives a lot of multi-hop messages within a short period of time. The client reacts to this by allocating more memory. If multi-hop messages are sent over the default monitor binding, the message coming from the memory server will be blocked, therefore this will result in a dead lock. By creating new monitor bindings and not using the default monitor binding, we can prevent such a scenario. 182 Multi-hop messages carry a virtual circuit identifier (VCI). Virtual circuit identifiers allow nodes to identify the particular multi-hop channel a message belongs to. Each node on a multi-hop channel maintains a forwarding table, which maps VCIs to the next hop on that particular channel. A node forwards multi-hop messages based on this forwarding table. At channel end-points, a VCI allows to identify the binding belonging to the multi-hop channel the message was sent over. Virtual circuit identifiers are not only local to a specific link, but also to a direction on that link. Figure~\ref{fig:vci} shows an example assignment of VCIs. 184 We assign virtual circuit identifiers at random. At each node, we use a hash table to map virtual circuit identifiers to a pointer to the channel state. The use of a hash table allows efficient message forwarding. When a message arrive [all...] |
/barrelfish-2018-10-04/doc/011-idc/ |
H A D | IDC.tex | 96 alias \> call \> enum \> in \> interface \> message \\ 157 \item A simple message specification, using either the \texttt{message}, 159 single unidirectional message with typed arguments, 160 and described in Section~\ref{sec:lang:message}. 170 one message in every interface. 231 \subsection{Simple message}\label{sec:lang:message} 233 A simple message specification takes the form: 237 message|cal [all...] |
/barrelfish-2018-10-04/usr/eclipseclp/Flexlm/ |
H A D | bip_pt.c | 207 char *message = lp_errstring(lp_handle); local 208 if (!message) /* shouldn't happen */ 209 message = ""; 210 Make_String(&pw, message); 216 char *message = lp_warning(lp_handle); local 228 if (message) 231 Make_String(&pw, message);
|
/barrelfish-2018-10-04/lib/pcre/ |
H A D | pcreposix.c | 213 const char *message, *addmessage; local 216 message = (errcode >= (int)(sizeof(pstring)/sizeof(char *)))? 218 length = strlen(message) + 1; 227 sprintf(errbuf, "%s%s%-6d", message, addmessage, (int)preg->re_erroffset); 230 strncpy(errbuf, message, errbuf_size - 1);
|
/barrelfish-2018-10-04/lib/rcce/ |
H A D | ring_barriers.c | 73 static void message(void) function 218 // Wait til previous message has been processed by receiver 287 message(); 289 message(); 295 message(); 297 message();
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/userman/ |
H A D | umssocket.tex | 121 [eclipse 27]: printf(s, "%w. %b", message(client)), read(s, Msg). 127 printf(news, "%w. %b", message(server)). 129 Msg = message(client) 133 Msg = message(server) 144 The communication protocol does not guarantee that the message 146 Every packet represents a message which is read separately 151 a message with clear boundaries.} 159 This connection can be temporary, and after writing the message 181 the sender has to identify itself explicitly in the message 186 a hello message fro [all...] |
/barrelfish-2018-10-04/lib/libc/rpc/ |
H A D | getnetconfig.c | 654 const char *message; local 658 message = _nc_errors[0]; 661 message = _nc_errors[1]; 664 message = _nc_errors[2]; 667 message = _nc_errors[3]; 670 message = _nc_errors[4]; 673 message = "Unknown network selection error"; 676 return ((char *)message); 680 * Prints a message onto standard error describing the reason for failure.
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/mpslib/ |
H A D | eclipse.tex | 26 \cite{pvm:parcom4_94} have made the message passing paradigm very 34 one should take into account that message latencies are much higher 66 manager. High message latencies, typical for computer networks, may have 77 message passing primitives for hiding considerable network latencies. 89 unnecessary by for example low polling frequencies or time consuming message 91 will be sent it is appealing to avoid message polling and rely on active 96 parallel \eclipse would be relieved from the complexities of message 99 In addition to the more specific message passing requirements of parallel 102 quite well supported by most message passing libraries including
|
H A D | outline.tex | 38 been enhanced with a message passing system that eases the construction 39 of distributed applications. This note introduces the message passing 65 scope by basing its design and implementation on message passing 69 Parallel \eclipse hides its underlying message passing system from 70 the \eclipse application developer. The message passing capabilities 75 the message passing functionality of parallel \eclipse available to 80 message passing system. It is a high level abstraction of the 81 message passing facilities offered by the C-libraries AMSG, BMSG, 83 illustrates the utilisation of the \eclipse message passing 95 \eclipse message passin [all...] |