inet   Frontpage - Services - Products - Support - Company - Contact - Blog
Note that all opinions, views, etc. expressed in these blog pages reflect those of the authors, not necessarily those of Inferno Nettverk A/S.  

The Inferno Nettverk Blog

Using gdb(1), ps(1) and watch(1) to debug memory leaks

Posted by Michael Shuldman, Inferno Nettverk A/S, Norway on Fri May 9 14:05:10 MEST 2014
0 comments

Even though we use automated tools for helping us detect when and where memory leaks occur, like the excellent Valgrind system, as well as commercial static analysis systems, none of the external tools used were able to warn about a problem we recently had. Fortunately the problem was however detected by our in-house test system, rather than a customer when our test system started generating messages like this:

Random Observations (1) - top(1) application CPU usage definition

Posted by Inferno Nettverk A/S, Norway on Sat Jan 4 02:38:22 MET 2014
0 comments

This blog posting contains some random observations made during software development, regarding problems that were not easily solved by searching the Internet for solutions explaining what was going on. Perhaps these entries will help others in a similar situation by making the information more available. Question: What does the 'top' application CPU percentage value include?

Livedebug: the art of dumping core and dying on live production systems

Posted by Michael Shuldman, Inferno Nettverk A/S, Norway on Sat Aug 3 22:42:07 MEST 2013
0 comments

When a customer reports a problem with our software, we work hard to figure out what is going on as fast as possible, usually with no access to the system where our software is running in production. Depending on the SLA we have with the particular customer and how serious the problem is, this may involve waking up the right developer in the middle of the night to start analysing the problem.

Valgrind and uninitialised reads debugging

Posted by Michael Shuldman, Inferno Nettverk A/S, Norway on Tue Dec 20 16:46:39 2011
1 comment

Valgrind is a useful tool for discovering many types of programming errors at runtime, and here at Inferno Nettverk, Valgrind is part of the automated testing system for our software. That means I don't spend much time thinking about or running Valgrind myself, but now and then I get an email from the test system complaining that Valgrind has detected an error.

Copyright © 1998-2014 Inferno Nettverk A/S