view doc/log-signals.dox @ 31519:0c0b94fb9ac7

oscar: Fix a memleak on receipt of messages ==32109== 2,981 bytes in 7 blocks are definitely lost in loss record 18,095 of 18,342 ==32109== at 0x4C244E8: malloc (vg_replace_malloc.c:236) ==32109== by 0x90D8534: g_malloc (gmem.c:132) ==32109== by 0x1613A408: byte_stream_getstr (bstream.c:167) ==32109== by 0x161434B3: incomingim (family_icbm.c:928) ==32109== by 0x161440A4: snachandler (family_icbm.c:2112) ==32109== by 0x1614B4D2: flap_connection_recv (flap_connection.c:776)

/** @page log-signals Log Signals

 @signals
  @signal log-timestamp
 @endsignals

 @see log.h

 <hr>

 @signaldef log-timestamp
  @signalproto
char *(*log_timestamp)(PurpleLog *log, time_t when, gboolean show_date);
  @endsignalproto
  @signaldesc
   Emitted to allow plugins to customize the timestamp on a message
   being logged.
  @param log       The log the message belongs to.
  @param when      The time to be converted to a string.
  @param show_date Whether the date should be displayed.
  @return A textual representation of the time, or @c NULL to use a
          default format.
  @note Plugins must be careful of logs with a type of PURPLE_LOG_SYSTEM.
 @endsignaldef

*/
// vim: syntax=c.doxygen tw=75 et