test suite reviews and discussions
 help / color / mirror / Atom feed
From: Zhimin Huang <zhiminx.huang@intel.com>
To: dts@dpdk.org
Cc: Zhimin Huang <zhiminx.huang@intel.com>
Subject: [dts] [PATCH V2 2/2] test_plans/shutdown_api_test_plan:add case in plan
Date: Thu, 13 Jan 2022 19:35:52 +0800	[thread overview]
Message-ID: <20220113113552.14517-2-zhiminx.huang@intel.com> (raw)
In-Reply-To: <20220113113552.14517-1-zhiminx.huang@intel.com>

add asan build test case in plan.

v2:
- fix plan format issue

---
 test_plans/shutdown_api_test_plan.rst | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/test_plans/shutdown_api_test_plan.rst b/test_plans/shutdown_api_test_plan.rst
index 5a44b78d..c1a7abae 100644
--- a/test_plans/shutdown_api_test_plan.rst
+++ b/test_plans/shutdown_api_test_plan.rst
@@ -254,3 +254,17 @@ Test Case: RX/TX descriptor status
 3. Check rx descriptor status can be ``AVAILABLE``, ``DONE`` or ``UNAVAILABLE``.
 4. Run ``show port 0 txq * desc * status`` to check tx descriptor status.
 5. Check tx descriptor status can be ``FULL``, ``DONE`` or ``UNAVAILABLE``.
+
+Test Case: RX/TX test with ASan enable
+--------------------------------------
+
+1. `AddressSanitizer<https://github.com/google/sanitizers/wiki/AddressSanitizer>`
+
+(ASan) is a widely-used debugging tool to detect memory access errors.
+Add "-Dbuildtype=debug -Db_lundef=false -Db_sanitize=address" in meson build system to enable ASan tool::
+
+   CC=gcc meson -Denable_kmods=True -Dlibdir=lib -Dbuildtype=debug -Db_lundef=false -Db_sanitize=address --default-library=static x86_64-native-linuxapp-gcc
+   ninja -C x86_64-native-linuxapp-gcc -j 70
+
+2. Launch testpmd and check testpmd status
+3. Send packet and check testpmd forward packet successfully
-- 
2.17.1


      reply	other threads:[~2022-01-13  3:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 11:35 [dts] [PATCH V2 1/2] tests/shutdown_api:add asan test case Zhimin Huang
2022-01-13 11:35 ` Zhimin Huang [this message]

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=20220113113552.14517-2-zhiminx.huang@intel.com \
    --to=zhiminx.huang@intel.com \
    --cc=dts@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).