Issue 181 in libnfc: Memory leak and multiplaform incompatibility using log4c

0 views
Skip to first unread message

lib...@googlecode.com

unread,
Nov 25, 2011, 11:12:04 AM11/25/11
to libnfc...@googlegroups.com
Status: Feedback
Owner: rco...@il4p.fr
CC: adia...@il4p.fr, romain.t...@gmail.com
Labels: Type-Defect Priority-Medium

New issue 181 by rco...@il4p.fr: Memory leak and multiplaform
incompatibility using log4c
http://code.google.com/p/libnfc/issues/detail?id=181

log4c have been used to smart-log in libnfc but this logger is not
available under Windows for example.
Plus, valgrind reports memory leaks from log4c code.

log4c's author have been contacted, this project is not maintained anymore.

Now, we are looking for a good replacement, comments are welcome.

lib...@googlecode.com

unread,
Feb 27, 2012, 9:19:12 AM2/27/12
to libnfc...@googlegroups.com
Updates:
Status: Fixed

Comment #1 on issue 181 by rco...@il4p.fr: Memory leak and multiplaform

log4c fortunately dropped while reworking code for simplify types and API.

Reply all
Reply to author
Forward
0 new messages