summaryrefslogtreecommitdiff
path: root/src/or/command.c
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2006-10-18 15:41:46 +0000
committerNick Mathewson <nickm@torproject.org>2006-10-18 15:41:46 +0000
commit3c459a7397eff03f0f7f05f1089ad88af829de79 (patch)
treef9cff08e26449712ebc295248e522595c354bd33 /src/or/command.c
parent0c2109dd23da0fe975550ff142a6cf2038b5a6c2 (diff)
downloadtor-3c459a7397eff03f0f7f05f1089ad88af829de79.tar.gz
tor-3c459a7397eff03f0f7f05f1089ad88af829de79.zip
r9077@totoro: nickm | 2006-10-18 11:41:16 -0400
Another patch from Mike Perry; sprintfing a NULL pointer. (with comment). svn:r8747
Diffstat (limited to 'src/or/command.c')
-rw-r--r--src/or/command.c11
1 files changed, 10 insertions, 1 deletions
diff --git a/src/or/command.c b/src/or/command.c
index 9b30e2379d..405f766c98 100644
--- a/src/or/command.c
+++ b/src/or/command.c
@@ -384,7 +384,16 @@ command_process_destroy_cell(cell_t *cell, or_connection_t *conn)
reason == END_CIRC_REASON_REQUESTED) {
/* XXXX This logic is wrong. Really, we should report the fact that
* the circuit was closed because of a DESTROY, *and* we should report
- * the reason that we were given. -NM */
+ * the reason that we were given. -NM
+ * Hrmm. We could store the fact that we sent a truncate and the
+ * reason for this truncate in circuit_t. If we ever get a destroy
+ * that doesn't match this reason, we could complain loudly -MP
+ * That won't work for the cases where the destroy is not because of
+ * a truncate, though. The idea is that if we get a DESTROYED cell
+ * with reason 'CONNECTFAILED' and another DESTROYED cell with reason
+ * 'RESOURCELIMIT', the controller may want to know the reported
+ * reason. -NM
+ */
reason = END_CIRC_REASON_DESTROYED;
}
circuit_mark_for_close(circ, reason);