Debugging mTCP Applications
2009-04-26
Michael Brutman (mbbrutman@yahoo.com)


I would rather have you believe that mTCP is perfect, but we know
that nothing ever is.  But we can strive ...

Even if mTCP is acting normally you might still be having problems
related to your network or setup.  To make debugging and fixing
problems easier I have included some tracing features in the
library.

To turn on tracing you need to set two environment variables:

  set DEBUGGING=127
  set LOGFILE=logfile.txt


The DEBUGGING variable sets the level of detail to trace and the
LOGFILE says where to dump the trace too.  Here are the useful
values for DEBUGGING that you can use:

    1  Warnings only
  127  Full tracing except for packet contents
  255  Full tracing with some packet contents

The bigger the number the slower the machine will get.  Traces
can also get quite large.

If you have a trace that you would like me to read send it along
with a brief explanation of what you were doing and what your
network setup looks like.  I have been able to help a few people
get up and running this way and I have fixed countless of my own
bugs with it.

-Mike


Created April 26th, 2009, Last updated April 26th, 2009
(C)opyright Michael B. Brutman, mbbrutman@yahoo.com