Scott's r1a4 email reminded me to send this update: Recently, after asking Coverity about the ability to build multiple "flavors" of haiku with their software and publish the results separately, they created two separate "streams" for us: haiku-32bit and haiku-64bit in anticipation of eventual testing/scanning of the 64bit code separately. Yesterday, with some assistance from Alex Smith, I built his 64bit branch of Haiku with Coverity's software and submitted the results to the haiku-64bit stream. With the new Coverity website filtering, I was able to filter out results that are found in the haiku-64bit stream, but not in the haiku-32bit stream, and the number was pretty small - only 107 "defects" currently. This is likely because the 64bit images are very very small still ;) A few of the issues didn't appear to be related to the 64bit code, and are likely either: 1) new code changes since the last 32bit build was submitted, or 2) new issues found as a result of updates to Coverity's server-side analysis (they apparently updated it again recently). I will probably update the 32bit results again to help filter out the latter so that Alex can review 64bit specific issues more easily. If desired, I could request separate "powerpc" and "arm" streams as well - so we can begin identifying issues specific to each arch... and we could even begin adding streams for external/experimental branches where development outside of trunk is occurring. Any thoughts on that? - Urias