IPCTrace

• Download demo project - 41 Kb

Introduction

In the last few months I coded a lot of global hooks and out-of-process COM server related stuff. Global hooks are hard to debug because they're normally called in the context of the debugger process too. You can't use message boxes, etc. to report some action because this may cause your system to hang permanently under certain circumstances. There are tricks to resolve these problems (MSDN: Q179905), but I figured out problems under Windows 9x/Me. So I wrote my own inter-process tracer.

How it works

How to integrate

You should make a release build because you probably won't change any code of that project. To trace messages out of your application to the IPCTrace window I provided a macro called IPCTRACE. The definition of this macro can be found in the file IPCTraceMacros.h

#if (defined _DEBUG || defined _IPCRELEASETRACE)
#if (defined _DEBUG || defined _IPCRELEASETRACE)
#define IPCTRACE(message) \
{ \
    HWND hReceiver_CC976675_9794_4F03_B41C_FFB011BB8B8E = ::FindWindow(NULL, _T("IPCTrace")); \
    if (hReceiver_CC976675_9794_4F03_B41C_FFB011BB8B8E) \
    { \
        TCHAR szMessage[4096] = {'\0'}; \
        _stprintf(szMessage, _T("{P:%04d T:%04d} | "), ::GetCurrentProcessId(), ::GetCurrentThreadId()); \
        _tcscat(szMessage, message); \
        COPYDATASTRUCT cds; \
        ZeroMemory(&cds, sizeof(COPYDATASTRUCT)); \
        cds.dwData = 0x00007a69; \
        cds.cbData = _tcslen(szMessage) + sizeof(TCHAR); \
        cds.lpData = szMessage; \
        ::SendMessage(hReceiver_CC976675_9794_4F03_B41C_FFB011BB8B8E, WM_COPYDATA, NULL, (LPARAM) &cds); \
    } \
}
#else // defined _DEBUG || defined _IPCRELEASETRACE
#define IPCTRACE (void(0))
#endif // !_DEBUG

As you can see it is very simple. To use this macro include the IPCTraceMacros.h header and call the macro like this:

void CAnyClass::AnyFunc(...)
{
  IPCTRACE(_T("Trace this text..."))
}

An additional feature is that you can enable tracing in your release builds too! As you see in the code sample above you can define _IPCRELEASETRACE at the preprocessor definitions of your release build settings in order to make the macro work.

This updated version traces the corresponding process and thread ID to the output window.

In order to test this I supplied a simple client application called IPCTraceClient which is included in the package too. Try it and you'll see how it works...

If you need help with this or have suggestions how to improve it or state bugs feel free to drop me an email. Updated versions may be found at http://www.nitrobit.com/ or http://www.codecommunity.com/.

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here