Update README and minor tweaks

README.md

@@ -7,15 +7,13 @@
 <br/>
 [![Community Discord Link](https://img.shields.io/badge/Chat%20on%20(the%20very%20small)-Community%20Discord-blue?labelColor=2C3239&color=7289DA&style=flat&logo=discord&logoColor=959DA5)](https://discord.gg/7kv5AuCndG)
 
-🚧 WIP 🏗️
+Cpptrace is a lightweight C++ stacktrace library supporting C++11 and greater on Linux, macOS, and windows including
-
+mingw and cygwin environments. The goal: Make stack traces simple for once.
-Cpptrace is a lightweight C++ stacktrace library supporting C++11 and greater on Linux, Unix, macOS and Windows. The goal:
-Make stack traces simple for once.
-
-Support for cygwin/mingw will be added soon.
 
 Some day C++23's `<stacktrace>` will be ubiquitous. And maybe one day the msvc implementation will be acceptable.
 
+🚧 WIP: This library is in beta. 🏗️
+
 ## Table of contents
 
 - [Cpptrace](#cpptrace)
@@ -23,10 +21,10 @@ Some day C++23's `<stacktrace>` will be ubiquitous. And maybe one day the msvc i
   - [How to use](#how-to-use)
     - [CMake FetchContent](#cmake-fetchcontent)
     - [System-wide installation](#system-wide-installation)
-    - [Conan](#conan)
-    - [Vcpkg](#vcpkg)
   - [Docs](#docs)
   - [Back-ends](#back-ends)
+  - [Library configurations](#library-configurations)
+  - [Testing Methodology](#testing-methodology)
   - [License](#license)
 
 ## How to use
@@ -44,6 +42,8 @@ FetchContent_MakeAvailable(cpptrace)
 target_link_libraries(your_target PRIVATE cpptrace)
 ```
 
+It's as easy as that. Cpptrace will automatically configure itself for your system.
+
 ### System-wide installation
 
 ```sh
@@ -51,7 +51,7 @@ git clone https://github.com/jeremy-rifkin/cpptrace.git
 # optional: git checkout <HASH or TAG>
 mkdir cpptrace/build
 cd cpptrace/build
-cmake .. -DCMAKE_BUILD_TYPE=debug -DBUILD_SHARED_LIBS=On
+cmake .. -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=On
 make
 sudo make install
 ```
@@ -64,7 +64,7 @@ git clone https://github.com/jeremy-rifkin/cpptrace.git
 # optional: git checkout <HASH or TAG>
 mkdir cpptrace/build
 cd cpptrace/build
-cmake .. -DCMAKE_BUILD_TYPE=debug -DBUILD_SHARED_LIBS=On
+cmake .. -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=On
 msbuild cpptrace.sln
 msbuild INSTALL.vcxproj
 ```
@@ -73,6 +73,7 @@ Note: You'll need to run as an administrator in a developer powershell, or use v
 studio to get the correct environment variables set.
 </details>
 
+<!--
 ### Conan
 
 TODO
@@ -80,6 +81,7 @@ TODO
 ### Vcpkg
 
 TODO
+-->
 
 ## Docs
 
@@ -108,7 +110,7 @@ namespace cpptrace {
 Back-end libraries are required for unwinding the stack and resolving symbol information (name and source location) in
 order to generate a stacktrace.
 
-The CMake script attempts to automatically choose a good back-end based on what is available on your system. You can
+The CMake script attempts to automatically choose good back-ends based on what is available on your system. You can
 also manually set which back-end you want used.
 
 **Unwinding**
@@ -126,11 +128,11 @@ can hold addresses for 100 frames (beyond the `skip` frames). This is configurab
 **Symbol resolution**
 
 | Library      | CMake config                             | Platforms             | Info                                                                                                                                                                                         |
-| ------------ | ---------------------------------------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ------------ | ---------------------------------------- | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| libbacktrace | `CPPTRACE_GET_SYMBOLS_WITH_LIBBACKTRACE` | linux, macos*, mingw* | Libbacktrace is already installed on most systems, or available through the compiler directly. If it is installed but backtrace.h is not already in the include path (this can happen when using clang when backtrace lives in gcc's include folder), `CPPTRACE_BACKTRACE_PATH` can be used to specify where the library should be looked for. |
+| libbacktrace | `CPPTRACE_GET_SYMBOLS_WITH_LIBBACKTRACE` | linux, macos*, mingw* | Libbacktrace is already installed on most systems or available through the compiler directly. For clang you must specify the absolute path to `backtrace.h` using `CPPTRACE_BACKTRACE_PATH`. |
-| libdl        | `CPPTRACE_GET_SYMBOLS_WITH_LIBDL`        | linux, macos          | Libdl uses dynamic export information. Compiling with `-rdynamic` is needed for symbol information to be retrievable.                                                                                                                                                                                                                          |
 | addr2line    | `CPPTRACE_GET_SYMBOLS_WITH_ADDR2LINE`    | linux, mingw          | Symbols are resolved by invoking `addr2line` via `fork()` (on linux/unix, and `popen` under mingw).                                                                                          |
 | dbghelp      | `CPPTRACE_GET_SYMBOLS_WITH_DBGHELP`      | windows               | Dbghelp.h allows access to symbols via debug info.                                                                                                                                           |
+| libdl        | `CPPTRACE_GET_SYMBOLS_WITH_LIBDL`        | linux, macos          | Libdl uses dynamic export information. Compiling with `-rdynamic` is needed for symbol information to be retrievable. Line numbers won't be retrievable.                                     |
 | N/A          | `CPPTRACE_GET_SYMBOLS_WITH_NOTHING`      | all                   | No attempt is made to resolve symbols.                                                                                                                                                       |
 
 *: Requires installation
@@ -160,6 +162,48 @@ possible. `CPPTRACE_HARD_MAX_FRAMES` is ignored.
 There are plenty more libraries that can be used for unwinding, parsing debug information, and demangling. In the future
 more back-ends can be added. Ideally this library can "just work" on systems, without additional installation work.
 
+## Library configurations
+
+Summary of all library configuration options:
+
+Back-ends:
+- `CPPTRACE_FULL_TRACE_WITH_LIBBACKTRACE`
+- `CPPTRACE_FULL_TRACE_WITH_STACKTRACE`
+- `CPPTRACE_GET_SYMBOLS_WITH_LIBBACKTRACE`
+- `CPPTRACE_GET_SYMBOLS_WITH_LIBDL`
+- `CPPTRACE_GET_SYMBOLS_WITH_ADDR2LINE`
+- `CPPTRACE_GET_SYMBOLS_WITH_DBGHELP`
+- `CPPTRACE_GET_SYMBOLS_WITH_NOTHING`
+- `CPPTRACE_UNWIND_WITH_UNWIND`
+- `CPPTRACE_UNWIND_WITH_EXECINFO`
+- `CPPTRACE_UNWIND_WITH_WINAPI`
+- `CPPTRACE_UNWIND_WITH_NOTHING`
+- `CPPTRACE_DEMANGLE_WITH_CXXABI`
+- `CPPTRACE_DEMANGLE_WITH_NOTHING`
+
+General:
+- `CPPTRACE_BACKTRACE_PATH`: Path to libbacktrace backtrace.h, needed when compiling with clang
+- `CPPTRACE_HARD_MAX_FRAMES`: Some back-ends write to a fixed-size buffer. This is the size of that buffer. Default is
+  `100`.
+
+Testing:
+- `CPPTRACE_BUILD_TEST`
+- `CPPTRACE_BUILD_TEST_RDYNAMIC`
+- `CPPTRACE_BUILD_SPEEDTEST`
+- `CPPTRACE_BUILD_SPEEDTEST_DWARF4`
+- `CPPTRACE_BUILD_SPEEDTEST_DWARF5`
+
+## Testing Methodology
+
+Cpptrace currently uses integration and functional testing, building and running under every combination of back-end
+options. The implementation is based on [github actions matrices][1] and driven by python scripts located in the
+[`ci/`](ci/) folder. Testing used to be done by github actions matrices directly, however, launching hundreds of two
+second jobs was extremely inefficient. Test outputs are compared against expected outputs located in
+[`test/expected/`](test/expected/). Stack trace addresses may point to the address after an instruction depending on the
+unwinding back-end, and the python script will check for an exact or near-match accordingly.
+
+[1]: https://docs.github.com/en/actions/using-jobs/using-a-matrix-for-your-jobs
+
 ## License
 
 The library is under the MIT license.

src/full/full_trace_with_libbacktrace.cpp

@@ -6,6 +6,7 @@
 
 #include <cstddef>
 #include <cstdint>
+#include <cstdio>
 #include <vector>
 
 #ifdef CPPTRACE_BACKTRACE_PATH
@@ -44,8 +45,8 @@ namespace cpptrace {
             frame.symbol = symbol ? symbol : "";
         }
 
-        void error_callback(void*, const char*, int) {
+        void error_callback(void*, const char* msg, int errnum) {
-            // nothing for now
+            fprintf(stderr, "Libbacktrace error: %s, code %d\n", msg, errnum);
         }
 
         backtrace_state* get_backtrace_state() {

src/platform/cpptrace_program_name.hpp

@@ -43,6 +43,7 @@ namespace cpptrace {
 }
 
 #elif defined(__linux__)
+
 #include <linux/limits.h>
 #include <sys/types.h>
 #include <unistd.h>

src/symbols/symbols_with_libbacktrace.cpp

@@ -5,6 +5,7 @@
 #include "../platform/cpptrace_program_name.hpp"
 
 #include <cstdint>
+#include <cstdio>
 #include <memory>
 #include <vector>
 
@@ -36,9 +37,8 @@ namespace cpptrace {
             frame.symbol = symbol ? symbol : "";
         }
 
-        void error_callback(void* data, const char* msg, int errnum) {
+        void error_callback(void*, const char* msg, int errnum) {
-            // nothing at the moment
+            fprintf(stderr, "Libbacktrace error: %s, code %d\n", msg, errnum);
-            ///fprintf(stderr, "Backtrace error %s %d %p\n", msg, errnum, data); // TODO: Eliminate
         }
 
         backtrace_state* get_backtrace_state() {