cpptrace
easyloggingpp
| cpptrace | easyloggingpp | |
|---|---|---|
| 2 | 2 | |
| 474 | 3,684 | |
| - | 1.0% | |
| 9.7 | 5.4 | |
| 4 days ago | 28 days ago | |
| C++ | C++ | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cpptrace
- CppTrace – Simple, portable, and self-contained stacktrace library for C++11
-
Is try-catch absolute NO in C++ robotics applications?
I am guessing how bad it really is to simply throw some custom exception along with useful message and status code along with stack trace instead of simply returning failure status code. This way we can have single try-catch at the top level function eliminating hundreds of if-checks. Inside that catch block we can print stack trace we will know exact call hierarchy and line number that caused exception. For example a cpptrace library define custom exceptions that extend std:: exceptions and inject stack trace that can be printed with simple function call. This will also eliminate any possible tricky bug that may get introduced by forgetting to check status code returned by any function since exceptions are forced to be dealt with or else we can get failure stack trace.
easyloggingpp
-
Easy logging A logging system for c++20
Easylogging++ https://github.com/abumq/easyloggingpp
-
Why use a logger library and not just std::cout ?
I am currently looking at a well written code base. I notice the author uses https://github.com/abumq/easyloggingpp to log messages. Why might they have done that rather than just use std::cout or std::ofstream? The software doesn't really have performance constraints (most of the time it's just sleeping) nor is it networked. What do logging libraries offer and when would I decide to use one?
What are some alternatives?
libassert - The most over-engineered C++ assertion library
spdlog - Fast C++ logging library.
rr - Record and Replay Framework
easyloggingpp - C++ logging library. It is extremely powerful, extendable, light-weight, fast performing, thread and type safe and consists of many built-in features. It provides ability to write logs in your own customized format. It also provide support for logging your classes, third-party libraries, STL and third-party containers etc.
stacktrace - C++ library for storing and printing backtraces.
glog - C++ implementation of the Google logging module
G3log - G3log is an asynchronous, "crash safe", logger that is easy to use with default logging sinks or you can add your own. G3log is made with plain C++14 (C++11 support up to release 1.3.2) with no external libraries (except gtest used for unit tests). G3log is made to be cross-platform, currently running on OSX, Windows and several Linux distros. See Readme below for details of usage.
Boost.Log - Boost Logging library
plog - Portable, simple and extensible C++ logging library
log4cplus - log4cplus is a simple to use C++ logging API providing thread-safe, flexible, and arbitrarily granular control over log management and configuration. It is modelled after the Java log4j API.
quill - Asynchronous Low Latency C++ Logging Library
Blackhole - Yet another logging library.