From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: question about SIGSEGV in datacopier_readable in libxl_aoutil.c Date: Tue, 3 Sep 2013 10:23:15 +0100 Message-ID: <5225AA83.5080005@citrix.com> References: <1378195018.7651.55.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1378195018.7651.55.camel@kazak.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: "xen-devel@lists.xensource.com" , Ian Jackson , Chunyan Liu List-Id: xen-devel@lists.xenproject.org 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