From: Jun Dong <junx.dong@intel.com>
To: dts@dpdk.org
Cc: lijuan.tu@intel.com, qingx.sun@intel.com, junx.dong@intel.com
Subject: [dts][V3 0/2] Add function to support ASan test
Date: Thu, 10 Feb 2022 10:49:50 +0800 [thread overview]
Message-ID: <20220210024952.2876-1-junx.dong@intel.com> (raw)
About ASan: AddressSanitizer a.k.a. ASan is a widely-used debugging tool to detect memory access
errors. It helps to detect issues like use-after-free, various kinds of buffer overruns in C/C++
programs, and other similar errors, as well as printing out detailed debug information whenever
an error is detected. ASan is integrated with gcc and clang and can be enabled via a meson option:
-Db_sanitize=address, See the documentation for details (especially regarding clang).
About ASan test: DTS adds one parameter named asan to control ASan test, It contains three steps:
- Append ASan build parameters to meson build options. this may open the function of ASan detect
memory access errors. if occuring memory access errors, the stack info will recorded in DTS log
- After all cases tested finish, analyze DTS log and redefine case test result according to whether
case log contain memory access error info. modify the result to failed if contain otherwise inherit
the original result.
- Generate ASan report to distinguish it from the original report.
V3:
framework/*: Add function to support ASan test
doc/*: Add ASan test user guide
conf/asan.cfg | 6 +
doc/dts_gsg/usr_guide/asan_test.rst | 59 +++++
doc/dts_gsg/usr_guide/index.rst | 1 +
framework/asan_test.py | 385 ++++++++++++++++++++++++++++
framework/dts.py | 14 +-
main.py | 6 +-
6 files changed, 466 insertions(+), 5 deletions(-)
create mode 100644 conf/asan.cfg
create mode 100644 doc/dts_gsg/usr_guide/asan_test.rst
create mode 100644 framework/asan_test.py
--
2.33.1.windows.1
next reply other threads:[~2022-02-10 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 2:49 Jun Dong [this message]
2022-02-10 2:49 ` [dts][V3 1/2] framework/*: " Jun Dong
2022-02-10 2:49 ` [dts][V3 2/2] doc/*: Add ASan test user guide Jun Dong
2022-02-27 14:22 ` Tu, Lijuan
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=20220210024952.2876-1-junx.dong@intel.com \
--to=junx.dong@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=qingx.sun@intel.com \
/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).