<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scaling Symbolic Execution to Large Software Systems · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2408.01909/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Thu, 05 Nov 2026 05:34:29 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2408.01909/feed.xml" rel="self" type="application/rss+xml" /><item><title>Scaling Symbolic Execution to Large Software Systems — mentioned by rramadass</title><link>https://news.ycombinator.com/item?id=50375318</link><guid isPermaLink="false">urn:hackerpapers:mention:2408.01909:50375318</guid><pubDate>Thu, 05 Nov 2026 04:48:13 GMT</pubDate><description>&lt;p&gt;No, that&amp;#x27;s not how to look at it. Obviously &amp;quot;all function calls&amp;quot; phrase cannot be absolute, but most can be caught with the analyzer giving one of proved/disproved/unknown result. The reason all cannot be caught is because pre/post are logical predicates on sets of values and are not part of the typing system. To understand that, you have to know how a static analyzer works and specifically two of its functions, &amp;quot;Data Flow Analysis&amp;quot; and &amp;quot;Symbolic Execution&amp;quot;. It is Symbolic Execution that does static checking without the need for the actual runtime values to be known. It basically &amp;quot;executes&amp;quot;…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2408.01909/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item></channel></rss>
