Skip to main content

The world's simplest log file

Back when I was doing embedded programming we had a debugging feature called 'pokeouts'. The idea was that the program could write a single character to the screen when some important even occurred.

Now writing single characters to the screen might not seem like a good way to do debugging. After all, these days we've got tons of disk space and can spew log files out and our CPUs are not burdened. But in embedded programming you tend to have little space and little time.

This system worked by having code that resembled the following:

pokeout: LD AH, 0Eh
INT 10h
RET

And to make things even easier we actually implemented this by hooking an interrupt so that programs didn't need to know whether the pokeout facility was available. They could safely do INT xxh for debugging output. This meant that the logging facility could be loaded onto a running system.

It's amazing how much information you can convey with single characters scrolling across the screen. It's easy to get critical area entry and exit (we used lots of combinations of ( ) [ ] { } < > followed by single characters to identify the area). You can build on that to output hexadecimal numbers easily. And individual events can be hooked individual characters.

I'd spend my days looking at these scrolling screens of characters waiting for a program to crash. Everything was on the screen.

For some high-speed systems the screen pokeout was too slow. We replaced the routine above with code that wrote the pokeouts into a circular buffer in memory. When the program finally crashed the buffer could be examined using a high-powered debugger like SoftICE to give us a trace of the program's final moments. It was the equivalent of an aircraft's 'black box'.

Comments

Popular posts from this blog

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it:


Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name.

There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly.

What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message:

Our system is unable to process last names that contain non-letters, please replace them with spaces.

Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your last name …

Importing an existing SSL key/certificate pair into a Java keystore

I'm writing this blog post in case anyone else has to Google that. In Java 6 keytool has been improved so that it now becomes possible to import an existing key and certificate (say one you generated outside of the Java world) into a keystore.

You need: Java 6 and openssl.

1. Suppose you have a certificate and key in PEM format. The key is named host.key and the certificate host.crt.

2. The first step is to convert them into a single PKCS12 file using the command: openssl pkcs12 -export -in host.crt -inkey host.key > host.p12. You will be asked for various passwords (the password to access the key (if set) and then the password for the PKCS12 file being created).

3. Then import the PKCS12 file into a keystore using the command: keytool -importkeystore -srckeystore host.p12 -destkeystore host.jks -srcstoretype pkcs12. You now have a keystore named host.jks containing the certificate/key you need.

For the sake of completeness here's the output of a full session I performe…

More fun with toys: the Ikea LILLABO Train Set

As further proof of my unsuitability to be a child minder (see previous post) I found myself playing with an Ikea LILLABO 20-piece basic set train.


The train set has 16 pieces of track (12 curves, two straight pieces and a two part bridge) and 4 pieces of train. What I wondered was... how many possible looping train tracks can be made using all 16 pieces?

The answer is... 9. Here's a picture of the 9 different layouts.


The picture was generated using a little program written in Processing. The bridge is red, the straight pieces are green and the curves are blue or magenta depending on whether they are oriented clockwise or anticlockwise. The curved pieces can be oriented in either way.

To generate those layouts I wrote a small program which runs through all the possible layouts and determines which form a loop. The program eliminates duplicate layouts (such as those that are mirror images of each other).

It outputs a list of instructions for building loops. These instructions con…