Why aren't my memory allocations showing up?

Make sure you #include < stdlib.h > when you call malloc, calloc, or realloc.
Why isn't my console output getting forwarded to the TC Output Pane?

Make sure you #include < stdio.h > when you call printf.
Why aren't spaces allowed in the path name?

Tenacious C uses a toolchain called MinGW to run the underlying compiler and debugger. MinGW is an open source port of many common linux tools, including gcc and gdb. And while this is a boon to the Windows programming world, MinGW unfortunately does not support spaces in the paths. From their web page :

MinGW may have problems with paths containing spaces, and if not, usually other programs used with MinGW will experience problems with such paths. Thus, we strongly recommend that you do not install MinGW in any location with spaces in the path name reference; i.e. you should avoid installing into any subdirectory of “Program Files” or “My Documents”, or the like.

In our internal testing, MinGW sometimes works when the source files/installation path contain spaces. Other times, the program will simply not compile, make, debug, etc.

So in order to save our users headaches, Tenacious C requires that paths not contain spaces. This is annoying, but without this restriction there would be as many complaints (or more) about error messages about spaces.

If we can figure out how to ensure MinGW always works with spaces, we’ll lift the restriction.