On 4/11/14, 2:37 AM, Nicolas B. Pierron wrote:
Thanks for doing this priority list, at least this make things clear. :) I would suggest to amend it as follow:6a. *reproducible* topcrash bugs 6b. fuzzblockers […] 9f. *non-reproducible* topcrash bugs - top-crash are not always coming with a clear STR, in such case we would mostly be wasting time at trying to reproduce something. The reproducible one should indeed be important as we are able to investigate them. On the other hand, the non-reproducible one should not block our work, while we are waiting for somebody to report an STR. - fuzzblocker are often related to a crash / assertion which is too noisy. The fuzzblocker flag was made such as we know which crash should be fixed first, as the assertion is masking all other crash and breaks the quality of reports of our Security Team.
I agree with nbp here. fuzzblockers should be higher up (near position 6, as suggested) - perhaps what Chris meant were "other fuzz bugs" in its place (position 11c).
"other fuzz bugs" could involve, among others, correctness issues which do not crash or assert, but give different values depending on the runtime flag.
-Gary _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
