Actions
Bug #380
openvm - ambiguous return value
Status:
New
Priority:
Normal
Assignee:
-
Category:
VM
Target version:
-
Start date:
02/02/2012
Due date:
% Done:
0%
Estimated time:
Description
In the internals functions, the return value are not always tested.
One example with _addPartition :
SPregistPart is called but it can fail if the number of partitions is > 32. But _addPartition will always return the same value, so this fail is unknown...
This is one example, there are a lot of similar examples (in my code too)
No data to display
Actions