Sorry for the confusion. I got your point. Inserting pdb.set_trace() in
multiple daemons does work. Thanks for correcting me.
Salman
From: mandar.v...@nttdata.com
To: salma...@live.com; openstack@lists.launchpad.net
Subject: RE: [Openstack] Development/Debugging
Date: Tue, 12 Jun 2012 04
Salman,,
I have asked these kinds of questions earlier. but there was no generic way
to debug the code by using pydev or eclipse.
Here is the link that suggest some code debug using devstack etc..
http://www.joinfu.com/2012/03/testing-essex-rc1-with-devstack-and-tempest/
It will help you.
@lists.launchpad.net] On
Behalf Of Salman Malik
Sent: Monday, June 11, 2012 10:49 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] Development/Debugging
Hi All,
I have been trying to get my head around the OpenStack functionality for a
while now but unfortunately haven't been able to grasp it. I am
...
Hope other people also share their experience.
Thanks again,
Salman
From: mandar.v...@nttdata.com
To: salma...@live.com; openstack@lists.launchpad.net
Subject: RE: [Openstack] Development/Debugging
Date: Tue, 12 Jun 2012 03:58:39 +
Salman,
I haven’t used UI tools like Pydev
... so it makes sense to go through each daemon at a time using pdb.
Not sure what you mean, but you can easily put set_trace() in multiple daemons
at the simultaneously, in fact it is useful to trace the flow across various
openstack services.
-Mandar
Awesome explaination Mandar.
Thanks,
Hitesh
On Tue, Jun 12, 2012 at 10:12 AM, Vaze, Mandar mandar.v...@nttdata.comwrote:
... so it makes sense to go through each daemon at a time using pdb.
Not sure what you mean, but you can easily put set_trace() in multiple
daemons at the
6 matches
Mail list logo
