MirBSD manpage: curs_trace(3), trace(3), _nc_tracebits(3), _traceattr(3), _traceattr2(3), _tracechar(3), _tracechtype(3), _tracechtype2(3), _tracedump(3), _tracef(3), _tracemouse(3)


curs_trace(3)       UNIX Programmer's Manual        curs_trace(3)

NAME

     _tracef, _tracedump, _traceattr, _traceattr2, _nc_tracebits,
     _tracechar, _tracechtype, _tracechtype2, _tracemouse, trace
     - curses debugging routines

SYNOPSIS

     #include <curses.h>

     void _tracef(const char *format, ...);
     void _tracedump(const char *label, WINDOW *win);
     char *_traceattr(attr_t attr);
     char *_traceattr2(int buffer, chtype ch);
     char *_nc_tracebits(void);
     char *_tracechar(const unsigned char ch);
     char *_tracechtype(chtype ch);
     char *_tracechtype2(int buffer, chtype ch);
     char *_tracemouse(const MEVENT *event);
     void trace(const unsigned int param);

DESCRIPTION

     The trace routines are used for debugging  the  ncurses  li-
     braries,  as  well as applications which use the ncurses li-
     braries. These functions are normally  available  only  with
     the  debugging  library  libncurses_g.a, but may be compiled
     into any model (shared, static,  profile)  by  defining  the
     symbol TRACE.

     The principal parts of this interface are the trace  routine
     which  selectively  enables  different tracing features, and
     the _tracef routine which writes formatted data to the trace
     file.

     Calling trace with a nonzero parameter opens the file  trace
     in  the  current  directory  for  output.   The parameter is
     formed by OR'ing values from the list of  TRACE_xxx  defini-
     tions in <curses.h>. These include:

     TRACE_DISABLE
          turn off tracing.

     TRACE_TIMES
          trace user and system times of updates.

     TRACE_TPUTS
          trace tputs calls.

     TRACE_UPDATE
          trace update actions, old & new screens.

     TRACE_MOVE
          trace cursor movement and scrolling.

MirBSD #10-current     Printed 2022-12-23                       1

curs_trace(3)       UNIX Programmer's Manual        curs_trace(3)

     TRACE_CHARPUT
          trace all character outputs.

     TRACE_ORDINARY
          trace all update actions. The old and new  screen  con-
          tents are written to the trace file for each refresh.

     TRACE_CALLS
          trace all curses calls. The parameters  for  each  call
          are traced, as well as return values.

     TRACE_VIRTPUT
          trace virtual character puts, i.e., calls to addch.

     TRACE_IEVENT
          trace low-level input processing, including timeouts.

     TRACE_BITS
          trace state of TTY control bits.

     TRACE_ICALLS
          trace internal/nested calls.

     TRACE_CCALLS
          trace per-character calls.

     TRACE_DATABASE
          trace read/write of terminfo/termcap data.

     TRACE_ATTRS
          trace changes to video attributes and colors.

     TRACE_MAXIMUM
          maximum trace level, enables all of the separate  trace
          features.

     Some tracing features are enabled whenever the trace parame-
     ter  is  nonzero.  Some features overlap. The specific names
     are used as a guideline.

RETURN VALUE

     Routines which return a value are designed  to  be  used  as
     parameters to the _tracef routine.

PORTABILITY

     These functions are not part of the XSI interface. Some oth-
     er curses implementations are known to have similar, undocu-
     mented features, but they are not compatible with ncurses.

SEE ALSO

     curses(3).

MirBSD #10-current     Printed 2022-12-23                       2

Generated on 2022-12-24 01:00:14 by $MirOS: src/scripts/roff2htm,v 1.113 2022/12/21 23:14:31 tg Exp $ — This product includes material provided by mirabilos.

These manual pages and other documentation are copyrighted by their respective writers; their sources are available at the project’s CVSweb, AnonCVS and other mirrors. The rest is Copyright © 2002–2022 MirBSD.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report — diffs preferred.

Kontakt / Impressum & Datenschutzerklärung