May
23
- Classifying Bugs (html)
- In this article I classify the bugs depending where in the life cycle of development they can be produced.
- Knowing which kind of bug we have will allow us to react sooner and reduce the response time.
- This is the base of futura papers about building secure software systems from a software engineering point of view.
- Continuous Integration Review (html)
- This a review and a new proposal of the building times in the Martin Fowler’s paper about Continuous Integration.
- Basically I propose an approach of fixed building times rather than build per commit leads in better results.
- GA Memory Leakage Detection system (GALD-v1.0)
- This is a simple but yet powerful tool to determine if our application is leaking memory. You don’t need to replace your actual malloc(), realloc(), calloc() or free() standard function, you only need to #include and you just will turn on the memory detector.
- It will help you showing in which file and line your code the memory leakage or double freeing has been produced, which will make easier to fix it.
- Your application will output traces when memory is allocated and freed which you interpret by yourself or use the script provided wich will display at the end the memory leakages and extra freed memory.
- GALD is, of course, not as smart as valgrind! But it is faster and has a more straightforward use. GALD do not emulate a CPU and will not show you garbage from the libraries you have used, just your own memory allocation bugs.
- Useful Polymorphism in C (html version)
- In this paper I introduce an easy way to apply a well-known feature of OO languages as is polymorphism to the C language. I have kept only the useful semantic of polymorphism avoiding the use of complex syntax to make C OO flavoured.
- It is quite self-contect with a lot of code inside and even being it a draft is straightforward to get the whole idea working in your own project.
