Results 31 - 40
of
424
Table III. Number of Warnings Produced by rccjava and Various Versions of Houdini/rcc Warnings per KLOC
2006
Cited by 16
Table 1. Functions of DM vs. requirements from early warning system Requirements imposed by early warning system Function of
"... In PAGE 9: ... Listing all possible combinations would yield a multi-dimensional table of all aspects. Here, we present the most important combinations of two dimensions in Table1 and Table 2. The requirements of describing different kinds of relations and novel relation incorporation will be dealt with in following subsections.... In PAGE 9: ... The requirements of describing different kinds of relations and novel relation incorporation will be dealt with in following subsections. In Table1 , we summarize the use of data mining for different functional requirements as reported in literature. In Table 2, we compare some commonly used data mining methods against the data mining functions mentioned above.... ..."
Table 13. Primarv warning message color codes. 1 Color Code I Warning Message 1
Table___doc_jecmics 0 Warning Catenation Warning: Possible 263 262
Table 2. Percentage of erors and warnings High Level Domain % of Erors % of Warnings com 21 31
Table 2: The warnings generated by Macroscope. Each cell contains the number of warnings followed by the percentage in paren- theses. Warnings are counted by definition. The errors are explained in the text below.
"... In PAGE 7: ... In some cases, of course, using extra tokens is actually desirable, and the warning can be consid- ered spurious. Table2 summarizes the warnings produced on our test suite. Warnings related to macros are counted by definition, not by use.... In PAGE 8: ... 4.1 Warnings We examine the warnings in Table2 to try to determine their causes and to see how they provide answers to the three questions above. Imperfect #ifdef extractions.... ..."
Table 5. Comparison of Erlang B and WarnSim results.
"... In PAGE 4: ... Validation of WarnSim: To validate WarnSim, we compare WarnSim simulation results with the prediction results of Erlang B model. Call blocking probabilities shown in Table5... ..."
Table 1. Comparison to other approaches: Number of warnings reported.
2004
"... In PAGE 13: ...able 1. Comparison to other approaches: Number of warnings reported. Besides a few hand-crafted examples used for unit testing, three benchmark applications [18] were analyzed: A discrete-event elevator simulator and two task-parallel applications, SOR (Successive Over-Relaxation over a 2D grid) and the Travelling Salesman Problem (TSP). Table1 shows the results. The three warnings issued by all approaches are benign: In the elevator example, the two warnings refer to a case where a variable is checked twice, similarly to the exam- ple in Figure 6.... ..."
Cited by 8
Table 6: Serious bugs and false warnings in Eclipse 3.0.1 for null dereference and redundant comparison to null (RCN) warnings
2005
"... In PAGE 6: ... Our goal in evaluating the analysis on production software was to count how many real bugs the analysis found, and also mea- sure the false warning rate. The results of this evaluation are shown in Table6 . We obtained this data by manually classifying each null-pointer and redundant null comparison warning by hand as either a serious bug or a false warning.... ..."
Cited by 13
Results 31 - 40
of
424