
Universal Debugger Interface Specification
A-1
Appendix A
A
UDI Error Numbers
In general, each service accepts a number of parameters and returns a UDI
error code. UDI error codes other than the value
UDINoError
(which has the
value 0) indicate an error has occurred. If the error code is negative, it is a
TIP–specific error that is not documented as a UDI error in general. Such error
codes can be passed to
UDIGetErrorMessage()
to retrieve a textual
representation of the error. Positive UDI error codes are defined here.
Number Error Name
Description
0
UDINoError
No errors have occurred.
1
UDIErrorNoSuchConfiguration
Indicates that the requested configuration is
not present in the configuration file. Returned
only from
UDIConnect
().
2
UDIErrorCantHappen
Indicates the existence of some condition
internal to the IPC Layer that, theoretically,
can’t happen. This error should never occur.
3
UDIErrorCantConnect
The IPC Layer is incapable of supporting the
connection. This may occur, for example, if
the IPC Layer imposes a limit on the number
of concurrent connections that can be
supported and the limit has been reached.
This error is returned only when a IPC–
imposed limitation is reached.
4
UDIErrorNoSuchConnection
Indicates that the Session parameter is
invalid. It can be returned only from functions
that accept a Session parameter.
5
UDIErrorNoConnection
Is returned from functions that require a pre–
established connection (virtually all UDI
functions), if no connection is currently
established. This error, then, can occur only
before a
UDIConnect
call, or after a
UDIDisconnect
that has closed the current
connection.