id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
21	log failures better: add caller stack	Brian Warner		"When a method fails, we can log some information about it (if that option is
turned on in the Tub). The information logged looks like this:

{{{
2007/09/08 19:10 -0700 [Negotiation,client] an outbound callRemote (that we sent to someone else) failed on the far end
2007/09/08 19:10 -0700 [Negotiation,client]  reqID=858, rref=<RemoteReference at 0x48b37174 [pb://onxnl2fpfqruabaku26fa4t5543vj3at@207.7.153.181:36611,127.0.0.1:36611/vdrive]>, methname=get
}}}

and includes the remote stack trace.

This information is missing the following useful pieces:

 * the RemoteInterface in use: that methname=get is hard to use without
   knowing exactly __which__ ""get"" method we're talking about
 * the stack trace (or at least the top-most frame) of the callRemote(),
   so we can find out __why__ we were sending this message
"	enhancement	new	major	eventually	logging	0.1.6