DACA Could Mean Fewer Bugs in Debian
Every piece of software written has bugs. From the insignificant to the showstopper, bugs are there despite the herculean efforts of developers. But thanks to a new Debian project, many previously undetected bugs may finally get squashed.
Raphael Geissert, multi-talented Debian developer, recently introduced Debian's new Automated Code Analysis project. Geissert describes DACA as,
Automated Code Analysis helps detect and fix bugs and other issues in source code. The project aims to give users easy access to a wide variety of tools to improve quality of software distributed by Debian, while giving the tool's developers a test bed, more visibility, and more feedback. This is achieved by running those tools on the complete Debian archive.
It seems to many outsiders waiting for the often delayed releases that Debian's main goal is stability and eradication of bugs, and that impression is not inaccurate. Debian has worked hard to earn its reputation as of one of the most stable Linux distributions. Still though, many bugs get through; many more than some developers can accept. DACA will consist of a stack of tools for running tests on the source code of Debian packages then provide bug reports to the developers.
The project is just getting started, so there are only two tools in the box, but many more are planned. One of the tools is cppcheck. cppcheck audits C/C++ code for real functionality bugs instead of syntax errors. These are the kind of bugs that usually pass through the compiling process with no error, leading developers to believe everything is fine. Though this tool is far from complete and new and more extensive operations are planned in the coming months and years, it does quite a few checks. Some include out of bounds checking, auto variables, and memory leaks.
The other tool available is checkbashisms. As the name implies, it checks for Bashisms, which are bash extensions that are not strictly POSIX compliant. The first round of these reports is available online.
Although the list is short right now, the number of tools is anticipated to grow to over twenty. Geissert says the major limitation is, "most of the tools are CPU-bound, limiting considerably the number of tools and time it takes to check the whole Debian archive." He has called for bug checking, reporting of false positives, tool evaluation, and hardware donations. See his full post for more information.
Susan Linton is a Linux writer and the owner of tuxmachines.org.
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
| Non-Linux FOSS: Seashore | May 10, 2013 |
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- myip
46 min 10 sec ago - Keeping track of IP address
2 hours 37 min ago - Roll your own dynamic dns
7 hours 50 min ago - Please correct the URL for Salt Stack's web site
11 hours 2 min ago - Android is Linux -- why no better inter-operation
13 hours 17 min ago - Connecting Android device to desktop Linux via USB
13 hours 45 min ago - Find new cell phone and tablet pc
14 hours 43 min ago - Epistle
16 hours 12 min ago - Automatically updating Guest Additions
17 hours 21 min ago - I like your topic on android
18 hours 7 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?



Comments
a DACA by any other name
Isn't this type of program more commonly known as a static analyzer?
Indeed it is, but the 2 cool
Indeed it is, but the 2 cool parts of this are that 1) it is a suite of static analysis tools (at the moment a C/C++ tool and a Shell tool) and 2) is that it is run automatically on the whole Debian archive.
I don't think this will make a massive difference for users, since commonly encountered bugs will presumably already be filed. What it will help with is rarely encountered, edge-case bugs, potential security vulnerabilities and possibly performance (although there is a chance the performance of some apps will go down as they put in extra checks and balances to fix bugs found during the static analysis).
'DACA Could Mean Less Bugs in Debian'
I think you mean 'fewer', unless they come by the bucketful.
'number of tools is anticipated to grow' Shouldn't that be 'expected'?