tabs ↹ over ␣ ␣ ␣ spaces

by Jiří {x2} Činčura

Bytes on paper

31 Aug 2016 1 mins Firebird, Programming in general

Last week I had bit of free time during afternoons and I was working on compression support in FirebirdClient. My initial code I’ve put together couple of weeks before was straightforward but eventually everything started to fall through cracks of edge cases and I had dig deeper and provide a lot more implementation than I’d like to.

And one of the (un)pleasant things while working on wire protocol level with Firebird is that there’s really not much clues for debugging and error messages. Kind of you have it either right completely or you’re doomed. The wire protocol is binary, of course. And basically every byte and sometimes even bit matters. So loosing some means a quick trouble. Not because I lost some bytes, but because you don’t know where. Especially if data is involved which makes it so much harder to step through in debugger.

Although I consider myself quite fluent with debugger, sometimes it’s too much to handle and big guns need to be deployed. In my case that means pen and paper.

Bytes on paper

I started comparing runs without compression and with compression, inflating the compressed data in helper code and trying to spot the difference. Luckily for me it was not far from beginning and I was able to find it quickly. Then it was just head-down-march-to-the-finish and moving onto the next problem.

Profile Picture Jiří Činčura is .NET, C# and Firebird expert. He focuses on data and business layers, language constructs, parallelism, databases and performance. For almost two decades he contributes to open-source, i.e. FirebirdClient. He works as a senior software engineer for Microsoft. Frequent speaker and blogger at