xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Rroach <2284696125@qq.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Subject: help
Date: Sat, 28 Nov 2020 22:32:38 +0800	[thread overview]
Message-ID: <tencent_11A93B706FAC57659EC62A5E5EBF22DEB705@qq.com> (raw)

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

Hi, I'm attempting to use address sanitizer in locating bugs in Xen 4-13, while use address sanitizer in tools modules, while I ran some basic instructions like xl, Xen report such bug:
=================================================================
==2863==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 296 byte(s) in 11 object(s) allocated from:
&nbsp; &nbsp; #0 0x7f5b91aefd28 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.3+0xc1d28)
&nbsp; &nbsp; #1 0x467997&nbsp; (/usr/bin/x86_64-linux-gnu-gcc-6+0x467997)

Indirect leak of 10 byte(s) in 1 object(s) allocated from:
&nbsp; &nbsp; #0 0x7f5b91aefd28 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.3+0xc1d28)
&nbsp; &nbsp; #1 0x467997&nbsp; (/usr/bin/x86_64-linux-gnu-gcc-6+0x467997)

SUMMARY: AddressSanitizer: 306 byte(s) leaked in 12 allocation(s).
/root/faultxen/tools/libs/toolcore/../../../tools/Rules.mk:224: recipe for target 'headers.chk' failed
make[5]: *** [headers.chk] Error 1

==7520==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 10 byte(s) in 1 object(s) allocated from:
&nbsp; &nbsp; #0 0x7fd1028c8d28 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.3+0xc1d28)
&nbsp; &nbsp; #1 0x7fd1022e43b9 in __strdup (/lib/x86_64-linux-gnu/libc.so.6+0x803b9)

SUMMARY: AddressSanitizer: 10 byte(s) leaked in 1 allocation(s).
=================================================================
It seems this bug is very low-level, and affects many basic operations, do you have any idea what cause such bugs?

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

             reply	other threads:[~2020-11-28 14:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-28 14:32 Rroach [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-23 10:23 help Marwa Hamza
2016-03-10 20:04 help Safa Hamza
2016-03-11 14:49 ` help Konrad Rzeszutek Wilk
     [not found]   ` <CAFwQ9hH6_7v57sw9c96GG=B9FdqFGn4WnDYO3RU5sLxEKQX7gg@mail.gmail.com>
     [not found]     ` <20160311152001.GJ5133@char.us.oracle.com>
2016-03-11 15:20       ` help Konrad Rzeszutek Wilk
     [not found]         ` <CAFwQ9hE_erNA4uCCpdKwWRdZXRF39YJ=mqo6dbOpeWkNdipyTA@mail.gmail.com>
2016-03-11 16:02           ` help Konrad Rzeszutek Wilk
2016-03-11 16:08             ` help Safa Hamza
2016-03-11 16:09             ` help Wei Liu
     [not found]               ` <CAFwQ9hFx_ctRJdPzuE03asqYwcdxAGPFii_Ns0WFk3dmrVSfBQ@mail.gmail.com>
2016-03-11 17:16                 ` help Wei Liu
2016-03-15 17:56                   ` help Julien Grall
2016-03-15 18:09                     ` help Konrad Rzeszutek Wilk
2016-03-15 18:16                       ` help Julien Grall
2016-03-15 18:21                         ` help Konrad Rzeszutek Wilk
2016-03-15 18:22                           ` help Julien Grall
2016-03-15 21:01                   ` help Safa Hamza
2016-03-15 23:47                     ` help Doug Goldstein
2015-07-23 15:05 Help Akash Talole
2015-07-24  7:46 ` Help Wei Liu
2015-07-03  8:45 Help Akash Talole
     [not found] <557FA708.7020101@yahoo.fr>
2015-06-25  4:51 ` Help Luc Pierard de Maujouy
2015-06-25  8:51   ` Help Ian Campbell
2013-03-23  7:51 Help Arun Kv
2013-03-25 10:54 ` Help George Dunlap
2011-10-28  4:15 Help Pankaj Kumar Biswas
2011-10-28  8:47 ` Help Ian Campbell

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=tencent_11A93B706FAC57659EC62A5E5EBF22DEB705@qq.com \
    --to=2284696125@qq.com \
    --cc=xen-devel@lists.xenproject.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).