summaryrefslogtreecommitdiff
path: root/trace.c
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2011-02-24 14:30:19 (GMT)
committerJunio C Hamano <gitster@pobox.com>2011-03-08 20:12:04 (GMT)
commitbbc30f996380eacd71ca061675d5d0c5f21c45d2 (patch)
treef4a2531496b943eb6339cffd71a251df3a83d6a7 /trace.c
parent94b3b3746456949d834ec7bf454da3db4eb439cf (diff)
downloadgit-bbc30f996380eacd71ca061675d5d0c5f21c45d2.zip
git-bbc30f996380eacd71ca061675d5d0c5f21c45d2.tar.gz
git-bbc30f996380eacd71ca061675d5d0c5f21c45d2.tar.bz2
add packet tracing debug code
This shows a trace of all packets coming in or out of a given program. This can help with debugging object negotiation or other protocol issues. To keep the code changes simple, we operate at the lowest level, meaning we don't necessarily understand what's in the packets. The one exception is a packet starting with "PACK", which causes us to skip that packet and turn off tracing (since the gigantic pack data will not be interesting to read, at least not in the trace format). We show both written and read packets. In the local case, this may mean you will see packets twice (written by the sender and read by the receiver). However, for cases where the other end is remote, this allows you to see the full conversation. Packet tracing can be enabled with GIT_TRACE_PACKET=<foo>, where <foo> takes the same arguments as GIT_TRACE. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'trace.c')
0 files changed, 0 insertions, 0 deletions