April 2006
-
:
Ok, now I'm confused
I’ve been looking at my web server log analysis and I have three peaks in my graphs for the last few days. The first big peak, 6,000 hits per hour, was on 28th March when my relationship break-up post was on the front page of digg. … -
:
Deadlock detection tool updates
When I came back from skiing in Colorado I had a bug report from a client and it took me a fair while to isolate the problem for them. The report suggested that a server that I’d built for them a while back was deadlocking in certain … -
:
Comments disabled for a while
My hosting provider has changed something in their perl instalation which means that MT-Blacklist (the thing that protects this blog from comment and trackback spam) is broken and not doing its job properly. I’ve located a fix but … -
:
Comments and trackbacks are now back
I’ve fixed the MT-Blacklist problem and so comments and trackbacks are now working again. -
:
What this blog is ACTUALLY about
Given all the publicity that this blog has received recently over my relationship break-up I thought it might be a good idea to give any new visitors a jumping off point into some of the more popular technical pieces. Believe it or not, … -
:
TickShifter v0.1
Well, I figure that I’ve written about these debug tools that I’ve been working on for long enough. The time has come to make one available for other people to use and abuse. Given that I hope to sell some of these tools … -
:
TickShifter v0.2
As I mentioned a while back, I’ve been working on adding rudimentary GUIs to my debugging and testing tools. In fact, both the deadlock detection tool and the time shifting tool are both functional enough for real world use but the … -
:
Tools, debug thyselves
One of the first things that I tried to do with the latest release of my TickShifter tool was to run it on itself. Of course, that didn’t work. There are several reasons why the tool might have had problems running on itself but I … -
:
I love it when a plan comes together
Discovering and then fixing the problem that prevented my tools from running on themselves planted a seed of an idea in my mind. My APIHook library and any code that used it died horribly under leak testing tools such as Purify and … -
:
Hijacking a thread in another process
My API hooking currently relies on creating a block of memory in the target process to hold the string that you need to pass to LoadLibraryW() and then calling CreateRemoteThread() and passing the address of LoadLibraryW() as the thread …