Monday, March 6, 2017

LibLogging 1.0.6 released

liblogging 1.0.6 [download]

We have released liblogging 1.0.6.

This release mostly provides fixes for different issues, like a small memory leak, build detection for journal libraries and many more. For full details, see the changelog below.

sha256sum: 338c6174e5c8652eaa34f956be3451f7491a4416ab489aef63151f802b00bf93

----------------------------------------------------------------------------
v1.0.6 2017-03-06
- fix small memory leaks in libstdlog
  each open/close leaked a couple of bytes; this was no problem, except if
  they were called very often. However, it was a problem when using memory
  debuggers, which rightfully complained.
- fix BSD build
- enhancement:  sigsafe_printf now recognizes the "j" length modifier
  Thanks to David A. Bright for implementing this
- fix: build_file_line and build_syslog_frame call the __stdlog_print_*
  functions incorrectly
  Change these functions so that they call the __stdlog_print_* functions
  with the correct buffer size.
  see also: https://github.com/rsyslog/liblogging/issues/33
  Thanks to David A. Bright for the patch.
- Implement a STDLOG_PID option
  ... to specify that each log message should be tagged with the process
  identifier as well as the ident.
  Thanks to David A. Bright for implementing this
- bugfix: potentialSEGV in the stdlog_sigsafe_string formatter
  if NULL pointer was passed in
  Thanks to David A. Bright for the patch
- bugfix: stdlog_sigsafe_printf mis-handles an int or unsigned int
  Thanks to David A. Bright for the patch
- build system: auto-detect presence of journal libraries
  simplifies build for most users. Many complained on mailing list
  about missing journal dependency. Now by default we disable it if
  the libs are not found, what usually is the right thing to do.

No comments:

Post a Comment