I decided to do a bit of leak-finding by building debug Debian packages and
installing the results.
The leakfinder output is approximately useless. Here's why, courtesy of
gdbserver:
Reading symbols from
target:/usr/lib/x86_64-linux-gnu/vpp_plugins/dpdk_plugin.so...
Reading
/usr/lib/x86_64-linux-gnu/vpp_plugins/8b510bf9c83491fed12922b444b44503a5806c
.debug from remote target...
Reading
/usr/lib/x86_64-linux-gnu/vpp_plugins/.debug/8b510bf9c83491fed12922b444b4450
3a5806c.debug from remote target...
Reading
/usr/local/lib/debug//usr/lib/x86_64-linux-gnu/vpp_plugins/8b510bf9c83491fed
12922b444b44503a5806c.debug from remote target...
Reading
/usr/local/lib/debug/usr/lib/x86_64-linux-gnu/vpp_plugins//8b510bf9c83491fed
12922b444b44503a5806c.debug from remote target...
Reading
target:/usr/local/lib/debug/usr/lib/x86_64-linux-gnu/vpp_plugins//8b510bf9c8
3491fed12922b444b44503a5806c.debug from remote target...
(No debugging symbols found in
target:/usr/lib/x86_64-linux-gnu/vpp_plugins/dpdk_plugin.so)
This crude hack is sufficient to restore order:
diff --git a/src/pkg/debian/rules.in b/src/pkg/debian/rules.in
index 1958497f5..43c6efd9a 100644
--- a/src/pkg/debian/rules.in
+++ b/src/pkg/debian/rules.in
@@ -21,7 +21,7 @@ build3vers := $(shell py3versions -sv)
dh $@ --with $(DH_WITH) --buildsystem=pybuild
override_dh_strip:
- dh_strip --dbg-package=vpp-dbg
+ echo dont dh_strip --dbg-package=vpp-dbg
override_dh_install:
@for c in @VPP_COMPONENTS@; do \
It seems like we might want to skip the "dh_strip" step for debug Debians.
Is there a good way to do that?
FWIW... Dave
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20724): https://lists.fd.io/g/vpp-dev/message/20724
Mute This Topic: https://lists.fd.io/mt/88445441/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
