WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 1292] Memory leak in xend

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1292] Memory leak in xend
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 10 Jul 2008 08:08:50 -0700
Delivery-date: Thu, 10 Jul 2008 08:08:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1292-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1292





------- Comment #2 from jfehlig@xxxxxxxxxx  2008-07-10 08:08 -------
I have built tools/libxc with CFLAGS suitable for valgrind hoping to find the
leak in libxenguest or libxenctl, which are loaded in xend process.  I was able
to start xend in valgrind with

export XEND_DEBUG=1
export XEND_DAEMONIZE=0
valgrind --log-file=/tmp/xend-vg-out xend start

I then started/stopped some guests and attempted to terminate xend in order to
get a valgrind summary.  ctl-c results in

Exception starting xend:
Traceback (most recent call last):
  File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line
340, in run
    servers.start(status)
  File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvServer.py", line
159, in start
    time.sleep(100000000)
KeyboardInterrupt

Sending SIGTERM to xend process running in valgrind results in

[xend] DEBUG (SrvServer:77) SrvServer.cleanup()
[xend] DEBUG (XMLRPCServer:228) XMLRPCServer.cleanup()
[xend] DEBUG (XMLRPCServer:228) XMLRPCServer.cleanup()
[xend] DEBUG (Hald:50) Hald.shutdown()  pid:23302
[xend] DEBUG (XendDomain:611) cleanup_domains
Exception in thread HttpServer:
Traceback (most recent call last):
  File "/usr/lib64/python2.4/threading.py", line 442, in __bootstrap
    self.run()
  File "/usr/lib64/python2.4/threading.py", line 422, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.4/site-packages/xen/web/httpserver.py", line 312, in
run
    (sock, addr) = self.accept()
  File "/usr/lib64/python2.4/site-packages/xen/web/httpserver.py", line 331, in
accept
    return self.socket.accept()
  File "/usr/lib64/python2.4/socket.py", line 169, in accept
    sock, addr = self._sock.accept()
error: (22, 'Invalid argument')

Any hints on how to run xend in valgrind would be appreciated.  That said, if
the "leak" is in xend python code (e.g. ref not being released) any tips/tricks
on finding such leaks would also be greatly appreciated :-).  valgrind
obviously won't be much use if the leak is in xend python code.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>