[Twisted-Python] How to debug an AMP connection?

Peter Westlake peter.westlake at pobox.com
Fri Jul 24 13:43:55 EDT 2009

On Fri, 24 Jul 2009 12:01 -0400, "Jean-Paul Calderone"
<exarkun at divmod.com> wrote:
> On Fri, 24 Jul 2009 16:12:28 +0100, Peter Westlake
> <peter.westlake at pobox.com> wrote:

> >>  In general, though, if you're trying to debug Deferreds you might
> >>  try setting debugging with defer.setDebugging(1).
> >
> >What kind of output does that produce? I did try it, but didn't see
> >anything out of the ordinary.
> It makes Deferreds keep track of the call stack when they are created
> and when they are invoked.  This can be helpful tracking down
> Deferred failures that don't otherwise identify themselves very well.
> If you're not seeing any failures being logged, then this probably
> won't help much, since there won't be anything to increase the
> verbosity of. :)

That would explain it :-)

> Another thing to check out would be a network capture, to see if the
> server is actually sending back a response.  If not, then you know you
> should look at the server code more carefully.  If so, then the client
> code is probably at fault.

I tried that, and was somewhat overwhelmed by the amount of data!
But now I've found the python-pcapy package and I'm well on the
way to having a script that can match AMP commands and responses
and report any that don't match up. If it turns out to be useful,
I could post it, as long as my employers don't mind.

Thanks for the help,


More information about the Twisted-Python mailing list