iv_set_fatal_msg_handler(3) [debian man page]

iv_fatal(3)						    ivykis programmer's manual						       iv_fatal(3)

NAME

       iv_fatal, iv_set_fatal_msg_handler - ivykis fatal error condition handling

SYNOPSIS

       #include <iv.h>

       void iv_fatal(const char *fmt, ...);
       void iv_set_fatal_msg_handler(void (*handler)(const char *msg));

DESCRIPTION

       iv_fatal  aborts  the  running program, after possibly emitting an error message. The fmt parameter is a printf(3)-style format string, the
       message to be logged.

       If no handler is set (the default), the formatted message will be sent to syslog, with critical severity. Otherwise the handler as  set	by
       iv_set_fatal_msg_handler will be used instead.

       iv_fatal is also used internally by ivykis, whenever a fatal situation is detected.

       iv_set_fatal_msg_handler  can  be used to set an alternative (as opposed to syslog) function to call from iv_fatal, and its argument should
       be a function that does not return, and takes a single string as argument - the formatted error message.

SEE ALSO

       ivykis(3), iv_examples(3)

ivykis								    2012-06-18							       iv_fatal(3)

iv_thread(3)						    ivykis programmer's manual						      iv_thread(3)

NAME

       iv_thread_create, iv_thread_set_debug_state - ivykis thread convenience functions

SYNOPSIS

       #include <iv_thread.h>

       int iv_thread_create(char *name, void (*start_routine)(void *), void *arg);
       void iv_thread_set_debug_state(int state);

DESCRIPTION

       iv_thread_create  is a wrapper around pthread_create(3) which will maintain an ivykis main loop reference in the calling thread (which must
       be an ivykis(3) thread, i.e. have had iv_init(3) called in it) for as long as the created thread is alive.

       Maintaining a reference on the calling thread's ivykis event loop makes sure that the calling thread will not return from its  ivykis  main
       loop  before the created thread exits, as that could cause cleanup still happening in the created thread to be interrupted when the calling
       thread subsequently calls exit(3).

       The created thread need not be an ivykis thread.

       Enabling debugging by calling iv_thread_set_debug with a nonzero argument will print a debug message to standard error whenever a thread is
       created	via  iv_thread_create,	whenever  a  thread so created terminates normally by returning from its start_routine, self-terminates by
       calling pthread_exit(3), or is successfully canceled by pthread_cancel(3), and whenever destruction of such a thread is	signaled  back	to
       the calling thread.

       For inter-thread signaling, iv_thread uses iv_event(3).

SEE ALSO

       ivykis(3), iv_event(3), exit(3), pthread_cancel(3), pthread_create(3), pthread_exit(3)

ivykis								    2010-09-13							      iv_thread(3)