From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1645] The last EAL argument is replaced by the program name in argv[]
Date: Mon, 03 Feb 2025 03:56:02 +0000 [thread overview]
Message-ID: <bug-1645-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1645
Bug ID: 1645
Summary: The last EAL argument is replaced by the program name
in argv[]
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: nandinipersad361@gmail.com
Target Milestone: ---
The last EAL argument is replaced by program name in argv[] after
eal_parse_args is called. This is the intended behavior but it causes the
pointer to the last EAL argument to be lost.
Implication:
If the last EAL argument in argv[] is generated by a malloc function, changing
it will cause memory issues when freeing the argument.
Resolution/Workaround:
An application should not consider the value in argv[] as unchanged.
Affected Environment/Platform:
ALL.
Driver/Module:
Environment Abstraction Layer (EAL).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2992 bytes --]
reply other threads:[~2025-02-03 3:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-1645-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.