From: David Marchand <david.marchand@redhat.com>
To: 杨佳昊 <yang_jiahao@venusgroup.com.cn>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: confusion about dpdk asan
Date: Thu, 14 Sep 2023 10:25:29 +0200 [thread overview]
Message-ID: <CAJFAV8x9jF0aqsb5KKQRD+i_jVWxBm7OU0Spq-NKNKF9pv4+Eg@mail.gmail.com> (raw)
In-Reply-To: <a635771d7b829a14e162d4b19c422e635c32817f.359a2201.a2af.45bd.a515.90ba9723a42f@feishu.cn>
Hello,
On Thu, Sep 14, 2023 at 9:51 AM 杨佳昊 <yang_jiahao@venusgroup.com.cn> wrote:
>
> Hello
> I am tring to run dpdk example with asan.
> I have compile dpdk and example as directed by link https://github.com/DPDK/dpdk/blob/v21.11/doc/guides/prog_guide/asan.rst
> But I always get result as follow:
> =================================================================
> ==20078== ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x000000d28b92 sp 0x7ffc6a983b90 bp 0x7ffc6a983bb0 T0)
> AddressSanitizer can not provide additional info.
> #0 0xd28b91 (/root/dpdk-21.11/build/examples/dpdk-helloworld+0xd28b91)
> #1 0xd28fc1 (/root/dpdk-21.11/build/examples/dpdk-helloworld+0xd28fc1)
> #2 0xd2901d (/root/dpdk-21.11/build/examples/dpdk-helloworld+0xd2901d)
> #3 0x56dac3 (/root/dpdk-21.11/build/examples/dpdk-helloworld+0x56dac3)
> #4 0x7ff4b3eed554 (/usr/lib64/libc-2.17.so+0x22554)
> #5 0x56d958 (/root/dpdk-21.11/build/examples/dpdk-helloworld+0x56d958)
> ==20078== ABORTING
>
> It's not same as what i see in asan.rst.This result doesn't look right.
> My env:
> Gcc :9.3.0
> Libasan: 4.8.5
Hard to tell what is wrong here (especially without debug symbols).
Some quick questions for now:
Are you triggering this segfault with ASan disabled (iow: simply
configuring your build env with meson setup <build_dir>)?
Did you change something in DPDK or the example sources?
--
David Marchand
next prev parent reply other threads:[~2023-09-14 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 2:20 杨佳昊
2023-09-14 8:25 ` David Marchand [this message]
[not found] ` <a635771d7b829a14e162d4b19c422e635c32817f.f0d2fe5e.6b76.4a87.a832.a4fc4b015956@feishu.cn>
2023-09-14 10:42 ` David Marchand
2023-09-18 3:08 ` Stephen Hemminger
2023-09-18 2:53 ` 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=CAJFAV8x9jF0aqsb5KKQRD+i_jVWxBm7OU0Spq-NKNKF9pv4+Eg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=yang_jiahao@venusgroup.com.cn \
/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).