XtAppError() XtAppError()
Name
XtAppError - call the low-level error handler.
Synopsis
void XtAppError(app_context, message)
XtAppContext app_context;
String message;
Inputs
app_context
Specifies the application context.
message Specifies the error message to be reported.
Returns
XtAppError() terminates the application and does not return.
Description
XtAppError() passes its arguments to the installed low-level error handler. On POSIX systems, the default handler is _XtDefaultError().
It prints the message to the stderr stream and calls exit().
Usage
To report non-fatal error messages or warnings without exiting, use XtAppWarning() or XtAppWarningMsg(). To change the low-level error
handler, use XtAppSetErrorHandler().
XtAppError() calls the "low-level" error handler. It is better to use XtAppErrorMsg() which calls the "high-level" error handler. The
high-level handler looks up the error message in a resource database and so allows for customization and internationalization of error mes-
sages.
Although the Intrinsics interface allows separate error and warning handlers for each application context, most implementations will sup-
port only a single set of handlers. When a new handler is installed, it will be used in all application contexts.
See AlsoXtAppErrorMsg(1), XtAppSetErrorHandler(1), XtAppSetErrorMsgHandler(1), XtAppSetWarningHandler(1), XtAppSetWarningMsgHandler(1), XtAppWarn-
ing(1), XtAppWarningMsg(1),
XtErrorHandler(2). XtErrorMsgHandler(2).
Xt - Error Handling XtAppError()
Check Out this Related Man Page
XtAppError(3Xt) XT FUNCTIONS XtAppError(3Xt)NAME
XtAppError, XtAppSetErrorHandler, XtAppSetWarningHandler, XtAppWarning - low-level error handlers
SYNTAX
void XtAppError(app_context, message)
XtAppContext app_context;
String message;
void XtAppSetErrorHandler(app_context, handler)
XtAppContext app_context;
XtErrorHandler handler;
void XtAppSetWarningHandler(app_context, handler)
XtAppContext app_context;
XtErrorHandler handler;
void XtAppWarning(app_context, message)
XtAppContext app_context;
String message;
ARGUMENTS
app_context
Specifies the application context.
message Specifies the nonfatal error message that is to be reported. or the nonfatal error procedure, which usually returns
handler Specifies the new fatal error procedure, which should not return,.
message Specifies the message that is to be reported.
DESCRIPTION
The XtAppError function calls the installed error procedure and passes the specified message.
The XtAppSetErrorHandler function registers the specified procedure, which is called when a fatal error condition occurs.
The XtAppSetWarningHandler registers the specified procedure, which is called when a nonfatal error condition occurs.
The XtAppWarning function calls the installed nonfatal error procedure and passes the specified message.
SEE ALSO XtAppGetErrorDatabase(3Xt), XtAppErrorMsg(3Xt)
X Toolkit Intrinsics - C Language Interface
Xlib - C Language X Interface
X Version 11 Release 6.6 XtAppError(3Xt)
I am using tuxedo for our application.when i tried to compile my application, i get "PCC-F - NOERRFile , unable to open error message file, Facility PR2" error message..
Please let me know how to resolve it (0 Replies)
I am using xmake which I guess calls gmake which ... whatever.
I get an error in my compiling and want to know what the error number means. For example, the message might be "Error 139".
Rather then post the exact code fragment and exact output, I want to find the a list of error codes and... (1 Reply)
Hi friends,
I hope everyone is fine and doing well. I queried in my previous thread about the low-level qualities of C/C++ languages.I really thank you people for explaining, it was really helpful. One more ambiquity that I have in my mind is regarding the unix system calls like open, creat,... (1 Reply)
Hi friends,
I hope everyone is doing well and fine. I have always been hearing that C/C++ are relatively low-level as compared to Java/C# etc. Could you please tell me some low-level qualities of C/C++? And I think disk deframenters are written in C/C++, please correct me if I am wrong. And please... (5 Replies)