log4cpp

1. 基本概念 categories 日志的层级体系 appenders 日志打印到什么地方，可以是文件，也可以是终端 layouts 日志输出格式，定义类似于printf中的输出方式。有三种，后面都有例子，这三种分别是：basic，simple，pattern priority 日志的级别，所有的级别有： EMERG、FATAL、ALERT、CRIT、ERROR、WARN、NOTICE、INFO、DEBUG、NOTSET， 其中NOTSET < DEBUG < INFO < NOTICE < WARN < ERROR < CRIT < ALERT < FATAL = EMERG。 这个优先级的含义是：配置文件中设置了级别是debug，则任意的log都能打出来；如果配置了级别是fatal，则只有高于他优先级的日志才可以打印出来 additivity 限制appender会不会被继承(后面还有补充说明) 2. 程序举例 #include < stdio.h > #include < log4cpp / Category.hh > #include < log4cpp / FileAppender.hh > #include < log4cpp / SimpleLayout.hh > #define LOGFILE "./test.log" int main() { /*

I am implementing log4cpp im my project. See my Logger class implemented in the project. It is crashing in function doConfigure(initfile) defined in PropertyConfiguratorImpl.cpp file. More specifically in function call to _properties.load(in) call in Propertices.cpp file of the log4cpp: void Properties::load(std::istream& in)//_Chcount=0 in the expression value { clear(); std::string fullLine, command; std::string leftSide, rightSide; char line[256]; std::string::size_type length; while (in.getline(line, 256)) { fullLine = line; ................ .................//Remaining code of the

I've been trying for about 2 weeks now to get a logging library to work with. I've tried Log4cxx, Log4cpp, log4cplus and boost.log. The problem isn't that none of these work for me, it's that I can't figure out how to get them to work at all. I would really like to use log4cxx since I'm working with log4j/logback at work, but I haven't been able to get any of the libraries based on log4j to build. I've been able to build and use the boost library, but boost.log gives me all kinds of linker errors no matter what I try. If anyone could direct me to a step-by-step guide to get one of these

可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 问题: I am implementing log4cpp im my project. See my Logger class implemented in the project. It is crashing in function doConfigure(initfile) defined in PropertyConfiguratorImpl.cpp file. More specifically in function call to _properties.load(in) call in Propertices.cpp file of the log4cpp: void Properties::load(std::istream& in)//_Chcount=0 in the expression value { clear(); std::string fullLine, command; std::string leftSide, rightSide; char line[256]; std::string::size_type length; while (in.getline(line, 256)) { fullLine = line; ............

I've been wondering, what is the point of clog? As near as I can tell, clog is the same as cerr but with buffering so it is more efficient. Usually stderr is the same as stdout, so clog is the same as cout. This seems pretty lame to me, so I figure I must be misunderstanding it. If I have log messages going out to the same place I have error messages going out to (perhaps something in /var/log/messages), then I probably am not writing too much out (so there isn't much lost by using non-buffered cerr). In my experience, I want my log messages up to date (not buffered) so I can help find a crash