[vbox-dev] Bug report (major)

TwoThe twothe at web.de
Sun May 2 10:01:27 GMT 2010


Yes you are correct, it would be a bit too much to analyze all that code in such a short amount of time. ;)

I was experimenting with a (in my opinion) great static code analysis tool called Coverity and used my favorite VM software for testing it. The tool reported many more bugs than these, but most of them are minor or happen only in rare cases, when that bug won't make it worse anyway (i.e. out of memory states).

However the reports I currently have are only covering about 11% of the whole code, which is probably because I have not yet enabled the assembler checker (only C/C++ code is checked atm).

Am 02.05.2010, 02:26 Uhr, schrieb Alexey Eremenko <al4321 at gmail.com>:

> On Sat, May 1, 2010 at 12:51 AM, TwoThe <twothe at web.de> wrote:
>> Type: Bug
>> Severity: major
>> Component: VirtualBox OSE
>> Host: Ubuntu 64
> Hi TheTwo,
> Thank you very much for helping the project,
> But how could you, in such a short period of time, find several bugs?
> Is this manual code analysis, or some tool ?

More information about the vbox-dev mailing list