Maybe it's just that I'm not in this field, but I don't understand the context of this paper.<p>They say they have a "novel notion of <i>abstract debuggers</i>." But abstract execution is already a well-established concept, and isn't this just... that? Abstract execution is by definition examining the states that the program can be in...<p>They say, "Abstract debuggers are our way of making static analysis results legible to developers." Is the contribution here fundamentally about UI? (Not that that's a minor contribution -- good UI can make the difference between a successful product and an also-ran!)