From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 738] dpdk-ethtool has emory leak
Date: Wed, 16 Jun 2021 05:41:14 +0000 [thread overview]
Message-ID: <bug-738-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=738
Bug ID: 738
Summary: dpdk-ethtool has emory leak
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: zhihongx.peng@intel.com
Target Milestone: ---
Created attachment 161
--> https://bugs.dpdk.org/attachment.cgi?id=161&action=edit
asan patch
Environment
dpdk: 21.05
test patch: 0001-asan-and-asan-gcc-patch.patch
Test Setup:
1. git apply 0001-asan-and-asan-gcc-patch.patch
2. CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib -Dexamples=ethtool
-Dbuildtype=debug -Db_lundef=false -Db_sanitize=address
--default-library=static x86_64-native-linuxapp-gcc
3. ninja -C x86_64-native-linuxapp-gcc -j 110
4. ./x86_64-native-linuxapp-gcc/examples/dpdk-ethtool -l 16,15,14,13 -n 4
--file-prefix=dpdk_32767_20210616191235
5. EthApp> quit
6. expect result
no error
actual result
There are some errors here:
583 [[1m[[31m==598341==ERROR: LeakSanitizer: detected memory leaks^M
584 [[1m[[0m^M
585 [[1m[[34mDirect leak of 10024 byte(s) in 1 object(s) allocated from:^M
586 [[1m[[0m #0 0x7f3f21946ba8 in __interceptor_malloc
(/lib64/libasan.so.5+0xefba8)^M
587 #1 0xd3cb05 in cmdline_new ../lib/cmdline/cmdline.c:79^M
588 #2 0xd49616 in cmdline_stdin_new ../lib/cmdline/cmdline_socket.c:41^M
589 #3 0x4e3ace in ethapp_main ../examples/ethtool/ethtool-app/ethapp.c:907^M
590 #4 0x4e64fd in main ../examples/ethtool/ethtool-app/main.c:294^M
591 #5 0x7f3f20279492 in __libc_start_main (/lib64/libc.so.6+0x23492)^M
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-06-16 5:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 5:41 bugzilla [this message]
2021-10-26 6:43 ` [dpdk-dev] [Bug 738] [asan] " bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-738-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).