11:26 p.m.
------=_Part_477685_837648831.1362065174993
Content-Type: text/plain; charset=GBK
Content-Transfer-Encoding: 7bit
a debug environment in which to debug vdsm and node code line by line
thanks.
------=_Part_477685_837648831.1362065174993
Content-Type: text/html; charset=GBK
Content-Transfer-Encoding: 7bit
<div
style="line-height:1.7;color:#000000;font-size:14px;font-family:arial">a
debug environment in which to debug vdsm and node code line by
line<div><br></div><div>thanks.</div></div><br><br><span
title="neteasefooter"><span
id="netease_mail_footer"></span></span>
------=_Part_477685_837648831.1362065174993--
10:48 a.m.
Its not easy :) I hope it would
Vdsm its a multiprocess program. It runs simultaneously tasks and monitors them. You can
use GDB to debug the main process and watch threads step (if you want more information
about that i can help)
Otherwise I prefer the oldschool print debuging.. it always works great with VDSM. you
just need to add comment where you want to see the values or check if the program went
there. All you need to do is to edit the specific installed files (located at
/usr/share/vdsm) restart the service and wait for your print in the log..
Good luck
----- Original Message -----
From: "bigclouds" <bigclouds(a)163.com>
To: users(a)ovirt.org
Sent: Thursday, February 28, 2013 5:26:14 PM
Subject: [Users] how to debug vdsm and node codes
a debug environment in which to debug vdsm and node code line by line
thanks.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
11:14 a.m.
I normally use http://winpdb.org/about/ to attach to the vdsm
process. You can do it over the network even ;-)
----- Original Message -----
From: "Yaniv Bronheim" <ybronhei(a)redhat.com>
To: "bigclouds" <bigclouds(a)163.com>
Cc: users(a)ovirt.org
Sent: Thursday, February 28, 2013 5:48:52 PM
Subject: Re: [Users] how to debug vdsm and node codes
Its not easy :) I hope it would
Vdsm its a multiprocess program. It runs simultaneously tasks and
monitors them. You can use GDB to debug the main process and watch
threads step (if you want more information about that i can help)
Otherwise I prefer the oldschool print debuging.. it always works
great with VDSM. you just need to add comment where you want to see
the values or check if the program went there. All you need to do is
to edit the specific installed files (located at /usr/share/vdsm)
restart the service and wait for your print in the log..
Good luck
----- Original Message -----
From: "bigclouds" <bigclouds(a)163.com>
To: users(a)ovirt.org
Sent: Thursday, February 28, 2013 5:26:14 PM
Subject: [Users] how to debug vdsm and node codes
a debug environment in which to debug vdsm and node code line by line
thanks.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
4288
days inactive
4287
days old
2 comments
3 participants
participants (3)
-
Antoni Segura Puimedon -
bigclouds -
Yaniv Bronheim