From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1605] lib/eal build failure with address and undefined behavior sanitizers
Date: Tue, 17 Dec 2024 20:39:12 +0000 [thread overview]
Message-ID: <bug-1605-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1605
Bug ID: 1605
Summary: lib/eal build failure with address and undefined
behavior sanitizers
Product: DPDK
Version: 25.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
$ meson --werror -Db_sanitize=address,undefined build && ninja -C build
[..]
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: error: writing 4
bytes into a region of size 0 [-Werror=stringop-overflow=]
[..]
OS: Ubuntu 22.04
Compiler: gcc 11.2.0
Meson: 0.61.2
Ninja-build: 1.10.1
Build passes with "-Db_sanitize=address".
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2820 bytes --]
next reply other threads:[~2024-12-17 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 20:39 bugzilla [this message]
2024-12-18 16:52 ` [DPDK/core Bug 1605] lib/eal build failure with address and undefined behavior sanitizers Stephen Hemminger
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-1605-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.