{'fraction_non_alphanumeric': 0.030585106382978722, 'fraction_numerical': 0.0026595744680851063, 'mean_word_length': 4.976190476190476, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
When Does My Program Fail?

Oops! My program fails. Which are the circumstances under which this failure occurs? Answering this question is one of the first steps in debugging -- and a crucial one, as it helps characterizing, understanding, and classifying the problem. In this paper, we propose a technique to identify failure circumstances automatically. Given a concrete failure, we first compute the path condition leading to the failure and then use a constraint solver to identify, from the constraints in the path condition, the general failure conditions: "The program fails whenever the credit card number begins with 6, 5, and a non-zero digit." A preliminary evaluation of the approach on real programs demonstrates its potential usefulness.