Browsing All posts tagged under »testing«

Phil Koopman: Top 5 Embedded Software Problem Areas

May 31, 2016

0

The following resource is a thoughtful checklist that embedded software developers can take as inspiration to improve the product. It also links to further resources (as well as the author’s book) to explore the topics and analyze in depth the rationale of some of his suggestions. Better Embedded System SW: Top 5 Embedded Software Problem Areas – Five areas to dig into […]

Debian Nvidia driver issue with legacy card, solved.

November 4, 2013

7

On my Debian testing (jessie) computer, I usually perform a weekly “aptitude safe-upgrade“. This desktop has an old Nvidia GeForce 7300 GS card, and I’m using the “nvidia-kernel-dkms” package to provide proprietary drivers. On the last upgrade, Debian decided to install new packages with “nvidia-legacy-304xx” in their name. Other than that, a message appeared during […]

The development process of my Android app

March 26, 2013

1

I received a request from one of my readers, who wanted details on the development process of my Fake Dawn app. I wrote them a response and the mail has become quite consistent, so I decided to post it also on my blog, because it is a nice summary of what was going on in my […]

Mixing Debian testing and unstable packages

August 7, 2011

5

I installed Debian testing (wheezy) on my workstation about a month ago. Recently I wanted to install some packages, but they were not in the testing repository because they were blocked by the automatic rules that make a package transition from unstable to testing. For example, the arduino package was held down by gcc-avr and […]

Trace and profile function calls with GCC

October 6, 2010

59

Software debugging is a complex task. There is always the need to collect all available information, in order to detect and understand the problem fast and to think of a proper solution. Sometimes it’s more convenient to debug step-by-step, sometimes it’s better to make the program run completely, and then trace the execution flow “offline”. […]