Hi,
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 <[email protected]>:
On Sat, May 1, 2010 at 12:51 AM, TwoThe <[email protected]> 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 ?
_______________________________________________
vbox-dev mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-dev
