Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   10987 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

XtError()							     XtError()

Name
  XtError - call the low-level fatal error handler.

Synopsis
  void XtError(message)
	 String message;

Inputs
  message   Specifies the message to be reported.

Returns
  XtError() terminates the application and does not return.

Availability
  XtError() has been superseded by XtAppError().

Description
  XtError()  passes  its  arguments to the installed low-level error han‐
  dler.	 On POSIX systems, the default handler is _XtDefaultError().   It
  prints the message to the stderr stream and calls exit().

Usage
  XtError()  has been superseded by XtAppError(), which performs the same
  function on a per-application context basis.	XtError() now calls XtAp‐
  pError()  passing the default application context created by XtInitial‐
  ize().  Very few programs need multiple application contexts,	 and  you
  can  continue	 to use XtError() if you initialize your application with
  XtInitialize().  We recommend, however, that you use XtAppInitialize(),
  XtAppError(), and the other XtApp*() application context specific func‐
  tions.

  See XtAppError() for more information.

  XtError() 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 messages.

See Also
  XtErrorMsg(1), XtSetErrorHandler(1), XtSetWarningMsg(1), XtWarning(1),
  XtWarningMsg(1).

Xt - Error Handling						     XtError()

Vote for polarhome