The code just outputs some red text in a console. And that’s it. The code, hosted directly on this side is here:

#include <iostream>
#include <string>
#include <windows.h>

int main(int argc, char const *argv[])
{
    HANDLE hConsole = ::GetStdHandle(STD_OUTPUT_HANDLE);
    CONSOLE_SCREEN_BUFFER_INFO consoleScreenBufferInfo;
    ::GetConsoleScreenBufferInfo(hConsole, &consoleScreenBufferInfo);
    ::SetConsoleTextAttribute(hConsole, FOREGROUND_RED | FOREGROUND_INTENSITY);
    DWORD bytesWritten = 0;
    std::string msg("Hello there!\n");
    ::WriteConsole(hConsole, msg.data(), static_cast<DWORD>(msg.size()), &bytesWritten, 0);
    ::SetConsoleTextAttribute(hConsole, consoleScreenBufferInfo.wAttributes );

    return 0;
}

Over the years, web sites have evolved from static ones, where the only attack surface was the web server they ran on, to dynamic sites where PHP, and ASP.NET, amongst others, were subject to security issues.

With the increase in browser-side power, and the widespread use of AJAX, it now means that once again, websites can be generated statically, but comments can still be added via services such as disqus whilst having static HTML pages.

Powered by Twitter Tools

If you’re working with boost, there are Visual Studio debugger visualizers for VS2005/8/10 that can be found here.

Under the VS11 Beta, debugger visualizers have changed to an XML based description. See here and here for details and examples.

Then add

PS1='\[\033[32m\]\u@\h\[\033[00m\]:\[\033[34m\]\w\[\033[31m\]$(__git_ps1)\[\033[00m\]\$ '

to your .bashrc to get a bash prompt with colour.

Powered by Twitter Tools

Once again, I’ve come up against the infamous ‘application configuration is incorrect’. Fortunately, I’ve encountered this problem before.

Once again the problem was largely the same, and resolved in a similar fashion.

What happened?

The debug build of the application refused to start, ultimately due to a missing VC80 Debug CRT dll. This is not present on a clean Windows 7 machine, even with the VS2005 redist package applied.

How do you track it down?

Look at the event viewer, and it will report the missing dll. Using depends.exe doesn’t seem to report the information, and for some unknown reason sxstrace.exe refused to run correctly on my box.

The trick is to install cygwin and identify the offending static library by running

find . -name '*.lib' | xargs grep 'Microsoft.VC'

or

find . -name '*.lib' | xargs grep 'DebugCRT'

and look for the debug CRTs that are listed. For some reason the Powershell equivalent:

gci -include "*.lib" -recurse | select-string 'DebugCRT'

just displays all the binary/non-ascii characters and chokes the terminal, so if anyone knows how to resolve that, leave a comment below.

How do you fix it?

Rebuild whatever static library has been built against an older version of the DebugCRT. It is as simple as that. If it is third party code, you might have trouble.

Good News

Under VS2010 manifests are deprecated, so we don’t get this any more.

Moral of the Story

Ensure you rebuild all your static libraries in a new version of Visual Studio (even those you have checked in for convinience).