Finding Bug-Inducing Program Environments
Read the paper · arXiv:2304.10044
What this paper does with SQLancer
How it was classified
uses infrastructure — no
SQLancer is cited, not used; nothing in the mentions describes reusing its code.
extends technique — no
No technique is extended; the citation is background.
compares with — no
No empirical comparison against SQLancer is reported in the mentions.
describes as state of the art — no
The citation does not characterise SQLancer as the state of the art.
SQLancer publications it cites (2)
Bibliography entries that resolved to a SQLancer publication, or to a paper by one of the project's authors. A sentence citing one of these numbers is a reference to SQLancer even when it never writes the name.
| # | Entry | Matched as |
|---|---|---|
| 26 | Manuel Rigger and Zhendong Su. 2020. Finding Bugs in Database Systems via Query Partitioning. Proc. ACM Program. Lang. 4, OOPSLA, Article 211 (nov 2020), 30 pages. https://doi.org/10.1145/3428279 | sqlancer publication · TLP |
| 27 | Manuel Rigger and Zhendong Su. 2020. Testing Database Engines via Pivoted Query Synthesis. In 14th USENIX Symposium on Operating Systems Design and Implementation (OSDI 20). USENIX Association, 667–682. https://www.us... | sqlancer publication · PQS |
Every place it refers to SQLancer (2)
2 sentences, each stored verbatim from the extracted text with where it was found and how. “Citation marker” means the sentence names no tool at all and was reached through a reference number that resolved to a SQLancer publication.
| Id | Sentence | Found by | Where |
|---|---|---|---|
| M1 | For instance, there are domain-specific works on fuzzing a program’s configuration [ 6,16,44], databases [ 14,19,26,27,43,45], the network [7,11,24,29], et cetera. |
citation marker |
5.1 Performance analysis page 10 |
| M2 | , databases and programs) [14,19,26,27,43,45]. |
citation marker |
5.1 Performance analysis page 10 |