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" <[email protected]> > To: "bigclouds" <[email protected]> > Cc: [email protected] > 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" <[email protected]> > To: [email protected] > 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 > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
