Symbolic Execution
Symbolic execution is a program analysis technique that executes programs using symbolic (non-concrete) values instead of actual inputs, tracking how symbolic values flow through the program. Introduced by James C. King in 1976, symbolic execution builds mathematical constraints on program variables and can determine which inputs cause specific program behaviors, enabling automatic test generation and vulnerability detection. Modern symbolic execution tools like KLEE, S2E, and Z3 have become powerful instruments for finding subtle bugs and security vulnerabilities.
Rekod sumber
Petikan disalin secara verbatim daripada rekod sumber kaedah. Tiada pengesahan peringkat tuntutan disimpulkan daripadanya.
- King, J. C. (1976). Symbolic execution and program testing. Communications of the ACM, 19(7), 385-394. · DOI 10.1145/360248.360252
- Cadar, C., & Sen, K. (2013). Symbolic execution for software testing: Three decades later. Communications of the ACM, 56(2), 82-90. · DOI 10.1145/2408776.2408795
Tuntutan yang dikurasi
Tuntutan disimpan dalam lejar bukti, setiap satu dengan penilaiannya sendiri.
Pandangan ini tidak mencipta penilaian tuntutan apabila lejar tiada.
Kaedah berkaitan
Dijana daripada graf kaedah dan ditunjukkan sebagai perhubungan yang dicadangkan mesin — tiada tuntutan bukti disimpulkan.