rpcpdb 0.1.1

Debug support for RPC servers

Copyright (c) 2010-2011 Ben Bass <[e-mail]>

All rights reserved.

About

rpcpdb is a wrapper around the Python pdb debugger which makes it more suitable for use in RPC contexts.

It is designed to fulfil the need to debug a function on an already-running server which uses threads or processes to dispatch each remote procedure call, without having to change the source code to the server in any way. There is no disruption to other clients and rpc calls while the selected call is being debugged.

In particular, a mixin class is provided which adds the debug_func and undebug_func methods to your RPC server. These allow breakpoints to be controlled by another RPC client.

For an example, run the xmlrpc_server.py server process, then run one or more xmlrpc_client.py processes which will continually perform RPC requests against it. xmlrpc_debug.py can then be run to inject a debug breakpoint in a method which the clients are continually calling; the next client to call that function will be remotely debuggable, while other clients carry on oblivious.

Currently the debug interface is provided via a UNIX socket, but this will be extended in future.

RPC framework support is intended to cover XMLRPC, RPyC and Pyro in the initial stages.

Plans

• Add trigger criteria which check incoming arguments so the user can ensure the right client triggers the breakpoint

• Update examples, tidy up, document.

• Support other interfaces than termsock / UNIX socket.

License information

See the file “LICENSE” for information terms & conditions for usage, and a DISCLAIMER OF ALL WARRANTIES.

Changes

0.1

• first alpha release.

0.1.1

• fix issue where select call in termsock was continually finding writable FDs, causing 100% CPU usage