From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Chunyan Liu <cyliu@suse.com>
Subject: Re: question about SIGSEGV in datacopier_readable in libxl_aoutil.c
Date: Tue, 3 Sep 2013 10:23:15 +0100 [thread overview]
Message-ID: <5225AA83.5080005@citrix.com> (raw)
In-Reply-To: <1378195018.7651.55.camel@kazak.uk.xensource.com>
On 03/09/13 08:56, Ian Campbell wrote:
> On Tue, 2013-09-03 at 15:01 +0800, Chunyan Liu wrote:
>> Hi, List,
> Adding Ian J, who knows this bit of the code.
>
> Which version of Xen (and therefore libxl) are you using?
>
>> I'm trying to add migration APIs to libvirt libxl driver. In testing
>> HVM migration, on source side, when executing libxl_domain_suspend,
>> often meet SIGSEGV in libxl_aoutil.c: datacopier_readable, the
>> malloc() function place:
>> if (!buf || buf->used >= sizeof(buf->buf)) {
>> buf = malloc(sizeof(*buf));
>>
>> I doubt the heap is corrupted someway but couldn't confirm the root
>> cause. And I tried valgrind to find some clue, following is the info
>> right before the SIGSEGV.
>> #valgrind --leak-check=full /usr/sbin/libvirtd -l -d
> Did you use a Xen aware version of valgrind?
> http://blog.xen.org/index.php/2013/01/18/using-valgrind-to-debug-xen-toolstacks/
In which case I really should post my valgrind patches for full
migration support.
I will try to get around to posting the series today.
~Andrew
next prev parent reply other threads:[~2013-09-03 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 7:01 question about SIGSEGV in datacopier_readable in libxl_aoutil.c Chunyan Liu
2013-09-03 7:56 ` Ian Campbell
2013-09-03 9:23 ` Andrew Cooper [this message]
2013-09-03 14:31 ` question about SIGSEGV in datacopier_readable in libxl_aoutil.c [and 1 more messages] Ian Jackson
2013-09-04 8:15 ` Chunyan Liu
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=5225AA83.5080005@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=cyliu@suse.com \
--cc=xen-devel@lists.xensource.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).