From 78e94065fca63bfc3d00e77928554a440cd493a3 Mon Sep 17 00:00:00 2001 From: Laurent Pinchart Date: Wed, 13 Oct 2021 00:32:08 +0300 Subject: README: Document dependencies for backtrace generation libcamera now has the ability to use libdw and libunwind to generate backtraces, in addition to the glibc backtrace() function. libdw provides the most detailed output and is highly recommended, but is limited to parsing backtraces, it doesn't support capturing them. libunwind and backtrace() provide both features. If backtrace() is available, libunwind will not bring any improvement. Signed-off-by: Laurent Pinchart Reviewed-by: Paul Elder Reviewed-by: Umang Jain --- README.rst | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'README.rst') diff --git a/README.rst b/README.rst index 9ad0823d..8af5f118 100644 --- a/README.rst +++ b/README.rst @@ -63,6 +63,14 @@ for the libcamera core: [required] for IPA module signing: [required] libgnutls28-dev openssl +for improved debugging: [optional] + libdw-dev libunwind-dev + + libdw and libunwind provide backtraces to help debugging assertion + failures. Their functions overlap, libdw provides the most detailed + information, and libunwind is not needed if both libdw and the glibc + backtrace() function are available. + for the Raspberry Pi IPA: [optional] libboost-dev -- cgit v1.2.1