As those who make regular use of it probably already know, one of the features of Haiku's integrated debugger is the ability to inspect the contents of arbitrary (mapped) locations in the target team's address space. This can be handy in various instances, such as when trying to track down bugs that are likely due to a piece of code overwriting part of another data structure, since the data that's been written to memory might contain some pattern or even a familiar string that might hint at the culprit.

Statistics

The commit range this month is hrev48952-hrev49106. I got bored of doing the statistics by hand, so I've run the repo through gitstats instead. This gives more information than what I could do manually, including a listing of the most active commiters this month. Be sure to have a look at the results!

Development team of proprietary PVS-Studio C/C++ static analyzer presents their report on the source code of Haiku project in the article, which contains the review of the most suspicious code fragments they discovered.

While the Haiku developers are already using Coverity to identify some problems (mostly security related), PVS-Studio also detects code written in unusual ways or with possibly unexpected behavior. This means it can detect some functional issues, rather than just security problems.

The Haiku project is participating again in this year's "Semester of Code" (SoC) of the European VALS project. The SoC is similar to Google's GSoC, but without the financial incentive and more emphasis on the educational side.
This is the second installment of "SoC", the objective is still the same:

Its goal is to connect higher education students with open source projects to introduce them to the cooperative nature of working within a group on a bigger project. For Haiku, besides potentially extending its feature set, it's another opportunity to spark the interest of new, eager developers with a chance to gain future regular contributors.

There are currently 48 project proposals for Haiku on the VALS projects page.
If you're a student and interested to take on a project, you have to act quick: the deadline for your application ends on April, 1st 2015! Sorry for the late notice...

My contract has ended, but for now I have some free time to write a report every month about the ongoing development efforts from the Haiku team. I think this is a nice way to better see the work done, more so than looking at the roadmap progress bars which tend to not move much.

This month there were 91 commits (hrev48757-hrev48848). Let's see what's inside those.

As you probably have noticed, there were no weekly report in the previous weeks. The reason for this is that my contract is currently stopped. There is currently not enough money in Haiku's treasure chest to safely continue it. So, it's time to me to get back to "real life" and a full-time job in a software development company.

First of all I want to thank everyone who made this long contract possible by donating money to Haiku. It was a great experience for me, and a lot of fun as well. I did my best to move Haiku forward towards the R1 release. Unfortunately the beta 1 still isn't there, and we currently have 57 blocking tickets. It is a small number, but only the most complex or big issues are left.