See the sample report for an idea of that this program does.
TSM is a data management solution that is offered by IBM. It’s a huge, sprawling, flexible monstrosity that work perfectly… if you watch it and keep it fed and watered. TSM is also very scriptable and extensible.
This program attempts to give a TSM administrator a daily report that contains all the things that need to be periodically looked at. Wherever possible it will offer advice on how to fix problems found or attempt to resolve them itself. It will generate a nice email with the report and will modify the subject to flag and problems found so that you know when it’s really important to have a peek inside the report.
If you know of anything that you’d like added, you find a bug, or just can’t get it to run for you, please email me at [email protected] and I’ll see what I can do to help. Please Note: I no longer have regular access to a TSM system for testing, if you’d like troubleshooting I can probably work something remotely.
Thanks to the many people that have passed along code or suggestions and to the Wellcome Trust for funding my time at the University of Dundee.
Tired of guessing which compiler flags work best for your pet projects?
bench_gcc allows you to test the effect of different compiler flag (and compilers if you wish) on your source using real world tests. All you need is a target program (with source) and a scriptable test case.
Tags:
benchmarking code gcc shell-scripts utilities Posted on: September 22nd, 2004 under code.
Simple framework for integrating unit tests into C++ source files. Also contains some benchmarking routines and documentation on how to integrate it with automake.
This is just a refactoring of private code that I’ve used in several projects and have found useful &emdash; it’s not a substitute for a larger framework like CppUnit.
Tags:
benchmarking C++ code snippets unit-test Posted on: April 17th, 2004 under code.
Fast, thread safe C++ template with Least Recently Used (LRU) removal semantics. Complete with a comprehensive unit test suite. Threading features require the BOOST scientific library to be installed.
A validating malloc in less than 200 lines of code (excluding comments). It’s written in C++ using the STL for efficiency but all function are declared using C linkage so you can use them from either C or C++ very easily.
There are lots of debugging malloc implementations, why another? Most of the implementations that I’ve found have been huge or not easy to understand and modify. This implementation is simple and well documented. It’s easy to understand how it works and modify it’s behaviour of you don’t like something.
Currently it understands and tries to catch:
- Freeing already freed memory.
- Reallocing pointers not previously malloced.
- Over and under runs on malloced regions.
- Failure to free memory before program exit.
It also contains utility routines that:
- Hexdump regions on memory.
- Allow annotation of memory regions.
which are useful on their own. Examples are provided of all the above in the “examples” directory of the distribution.