test suite reviews and discussions
 help / color / mirror / Atom feed
From: Owen Hilyard <ohilyard@iol.unh.edu>
To: "Tu, Lijuan" <lijuan.tu@intel.com>
Cc: "Dong, JunX" <junx.dong@intel.com>, "dts@dpdk.org" <dts@dpdk.org>,
	 "Ling, WeiX" <weix.ling@intel.com>
Subject: Re: [RFC] [PATCH V1] framework/*: Add function to support ASan test
Date: Fri, 14 Jan 2022 08:44:11 -0500	[thread overview]
Message-ID: <CAHx6DYBvFam4V+h7cViBjbmYJD2z4JHtPG57mSmWKf_B_OA9Nw@mail.gmail.com> (raw)
In-Reply-To: <282c3927290f4e32bb893f6119f5777c@intel.com>

[-- Attachment #1: Type: text/plain, Size: 208 bytes --]

I think that using the filter_bounds approach makes sense.

Also, if we are open to adding other sanitizers, UBSAN might be fairly easy
to add, since it should be in roughly the same format as ASAN and LSAN.

[-- Attachment #2: Type: text/html, Size: 279 bytes --]

      reply	other threads:[~2022-01-14 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10  9:57 Dong JunX
2021-12-14 15:40 ` Owen Hilyard
2022-01-14 10:03   ` Tu, Lijuan
2022-01-14 13:44     ` Owen Hilyard [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=CAHx6DYBvFam4V+h7cViBjbmYJD2z4JHtPG57mSmWKf_B_OA9Nw@mail.gmail.com \
    --to=ohilyard@iol.unh.edu \
    --cc=dts@dpdk.org \
    --cc=junx.dong@intel.com \
    --cc=lijuan.tu@intel.com \
    --cc=weix.ling@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).