From afb8fe93b1cf1e44c15fc0e65c18eda67cc04da2 Mon Sep 17 00:00:00 2001 From: David Lamparter Date: Wed, 10 Nov 2021 12:16:40 +0100 Subject: doc: stick `libunwind` into build docs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It's strictly optional, but… the backtraces are really much better. Specifically, `libunwind` is notably more capable in figuring out function names compared to glibc/libexecinfo `backtrace_symbols()`. Signed-off-by: David Lamparter --- doc/developer/conf.py | 1 + 1 file changed, 1 insertion(+) (limited to 'doc/developer/conf.py') diff --git a/doc/developer/conf.py b/doc/developer/conf.py index 61df6e0e60..79f8233978 100644 --- a/doc/developer/conf.py +++ b/doc/developer/conf.py @@ -136,6 +136,7 @@ language = None # directories to ignore when looking for source files. exclude_patterns = [ "_build", + "building-libunwind-note.rst", "building-libyang.rst", "topotests-snippets.rst", "topotests-markers.rst", -- cgit v1.2.3