Simutrace 3.2.2
Simulation Tracing Framework
SimuBaseTypes.h File Reference
#include "SimuPlatform.h"

Enumerations

enum  ExceptionClass
 Type of exception. More...
 
enum  ExceptionSite
 Location of exception. More...
 
enum  RuntimeException
 Reason for runtime exception. More...
 
enum  NetworkException
 Reason for network exception. More...
 

Enumeration Type Documentation

The exception class specified to which group of exceptions the error belongs and allows to interpret the error code accordingly.

Since
3.0
Enumerator
EcUnknown 

The exception class is unknown

EcRuntime 

The exception has been generated by Simutrace in reaction to a runtime error such as an invalid argument to a function call

EcPlatform 

The exception has been generated by the operating system. The error code can be interpreted with the system supplied functions

EcPlatformNetwork 

The exception occurred in the network stack of the operating system. The error code can be interpreted with the system supplied functions

EcNetwork 

The exception has been generated by Simutrace due to an error in the communication with the server such as a malformed RPC message

EcUser 

The exception has been generated due to an error in a user-supplied callback routine

Since
3.2

Specifies if the exception occurred at the server or the client side.

Since
3.0
Enumerator
EsUnknown 

The exception site is unknown

EsClient 

The exception occurred on the client side

EsServer 

The exception occurred on the server side

Specifies the reason for runtime exceptions indicated by an exception class of EcRuntime.

Since
3.0
Enumerator
RteUnknownException 

The exception is unknown.

RteNotImplementedException 

The requested features is not (fully) implemented. Check for a newer version of Simutrace

RteNotFoundException 

The requested object (e.g., a file, a session, a stream, etc.) could not be found. The identifier does not point to a valid object or the object has been deleted by now

RteNotSupportedException 

The requested feature is not supported in the current configuration. This might for example be shared memory when using sockets. The error might also indicate that a feature is not supported by the current version of the client or server. Always use the client and server with the same version if possible

RteInvalidOperationException 

The requested operation is not valid in the current that of the object on which the operation should be performed, for example you cannot attach to a session which is already closing

RteOperationInProgressException 

The requested feature or object is not available at the moment due to an ongoing operation. Retrying the operation at a later time should generally fix this problem. You might encounter this exception if you try to read a stream segment that is currently still being processed (e.g., compressed) by the server

RteTimeoutException 

The requested operation did not finish in the specified amount of time

RteArgumentException 

One or more arguments supplied to a function are not valid. See the function's documentation for valid parameter values

RteArgumentNullException 

One or more pointer arguments passed to a function were NULL, but are expected to point to valid data or buffer space. See the function's documentation for more information

RteArgumentOutOfBoundsException 

The values for one or more arguments passed to a function were out of bounds. See the function's documentation for valid values

RteOptionException 

One or more command line options are not valid

RteConfigurationException 

The supplied configuration is not valid. See the documentation of libconfig for more information on the configuration format. See the sample configuration for a list of all valid options and their default values

RteUserCallbackException 

The user-supplied callback raised an exception or returned an error

Since
3.2

Specifies the reason for network exceptions indicated by an exception class of EcNetwork.

Since
3.0
Enumerator
NeUnknownException 

The network exception is unknown

NeRpcMessageMalformedException 

The RPC message received by the server or client was malformed and could not be interpreted. This can happen if the client and server are not compatible. Always use the same client and server version if possible

Karlsruhe Institute of Technology (KIT)
Operating Systems Group

http://simutrace.org
Generated by doxygen 1.8.10
Marc Rittinghaus