Monthly Archives: April, 2015

Diagrams with

Right now I am writing up network / system design paper for school, and I desperately needed a diagram tool, that I can use on any platform, and it can create pretty network diagrams. Guess what I’ve found a really good one!

( NOTE: The picture is NOT my actual diagram, just a sketch )


asterisk-gui on Ubuntu 14.10

Good news everyone!

While Ubuntu doesn’t seem to have asterisk-gui in their repository. It’s certainly possible to get it working! All one has to do first is follow this guide.

When that’s done ( the installation part, basically check out from SVN, configure, build, install, no big deal ), you are just a few commands away from a working asterisk-gui!

Unfortunately the make install command installs the web site to the wrong place ( on asterisk at least ). So will have to correct that, and also correct the permissions afterwards:

rm /usr/share/asterisk/static-http
ln -s /var/lib/asterisk/static-http /usr/share/asterisk/static-http
chmod asterisk /var/lib/asterisk -R
chgrp asterisk /var/lib/asterisk -R

Then restart Asterisk, and navigate to the following URL:

After logging in, and start-up configuration, you should see something similar to this:


That’s all folks!


Latest KDevelop plugin improvements

Hi there!
Let’s review what I’ve done to KDevelop’s kdev-cppcheck and kdev-valgrind plugins lately.

JSONized kdev-cppcheck and kdev-valgrind

This is fairly straightfoward: These plugins were still using the old .desktop plugin manifest files. Now they are using the embedded JSON manifests. This isn’t something user visible, but it’s needed as the old .desktop method is now deprecated.

Added the number of calls to the callgrind output of kdev-valgrind

Until now the callgrind output has only shown the IR and Inclusive IR fields. Now is shows the number of calls as well. Take a look at the pictures!


Reorganized the output of memcheck in kdev-valgrind

Until now kdev-valgrind’s memcheck output unfortunately didn’t show enough of the callstacks to be really useful. You couldn’t see where the problem exactly occured, or where it was stemming from! Now it shows the full backtrace + the auxilliary trace as well, so you can see what actually causes the problems. See the pictures!