From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 722] eal_save_args function has memory leak
Date: Fri, 28 May 2021 09:18:24 +0000 [thread overview]
Message-ID: <bug-722-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=722
Bug ID: 722
Summary: eal_save_args function has memory leak
Product: DPDK
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: zhihongx.peng@intel.com
Target Milestone: ---
Created attachment 157
--> https://bugs.dpdk.org/attachment.cgi?id=157&action=edit
asan meson patch
Environment
DPDK: 21.05
clang: 9.0.0
test patch: asan meson patch pmdinfogen-allow-padding-after-NUL-terminator.diff
Test Setup:
1. git apply pmdinfogen-allow-padding-after-NUL-terminator.dif
2. CC=clang meson --werror -Denable_kmods=True -Dbuildtype=debug
-Db_lundef=false -Db_sanitize=address x86_64-native-linuxapp-clang
3. ninja -C x86_64-native-linuxapp-clang -j 110
4. ./x86_64-native-linuxapp-clang/app/dpdk-testpmd -c 0x6 -n 4 – -i
5. testpmd> quit
6. expect result
quit normally
actual result
There are some errors here:
Detected memory leaks:
Direct leak of 3 byte(s) in 1 object(s) allocated from:
EAL: recvmsg failed, Bad file descriptor
EAL: recvmsg failed, Bad file descriptor
EAL: recvmsg failed, Bad file descriptor
EAL: recvmsg failed, Bad file descriptor
EAL: recvmsg failed, Bad file descriptor
EAL: recvmsg failed, Bad file descriptor
#0 0x573d94 in strdup
(/home/pzh/main_dpdk/x86_64-native-linuxapp-clang/app/dpdk-testpmd+0x573d94)
EAL: recvmsg failed, Bad file descriptor
EAL: recvmsg failed, Bad file descriptor
EAL: recvmsg failed, Bad file descriptor
#1 0x14f5ca5 in eal_save_args
/home/pzh/main_dpdk/x86_64-native-linuxapp-clang/../lib/eal/common/eal_common_options.c:232:17
EAL: recvmsg failed, Bad file descriptor
EAL: recvmsg failed, Bad file descriptor
EAL: recvmsg failed, Bad file descriptor
#2 0x155266f in rte_eal_init
/home/pzh/main_dpdk/x86_64-native-linuxapp-clang/../lib/eal/linux/eal.c:1002:2
EAL: recvmsg failed, Bad file descriptor
EAL: recvmsg failed, Bad file descriptor
EAL: recvmsg failed, Bad file descriptor
#3 0x80f964 in main
/home/pzh/main_dpdk/x86_64-native-linuxapp-clang/../app/test-pmd/testpmd.c:3752:9
EAL: recvmsg failed, Bad file descriptor
EAL: recvmsg failed, Bad file descriptor
#4 0x7fe863d22b96 in __libc_start_main
/build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-05-28 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 9:18 bugzilla [this message]
2021-09-22 9:44 ` 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-722-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).