<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>A New Era in Software Security: Towards Self-Healing Software via Large Language Models and Formal Verification · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2305.14752/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2305.14752/feed.xml" rel="self" type="application/rss+xml" /><item><title>A New Era in Software Security: Towards Self-Healing Software via Large Language Models and Formal Verification — mentioned by UncleEntity</title><link>https://news.ycombinator.com/item?id=46625081</link><guid isPermaLink="false">urn:hackerpapers:mention:2305.14752:46625081</guid><pubDate>Wed, 14 Jan 2026 22:53:47 GMT</pubDate><description>&lt;p&gt;I&amp;#x27;ve been working on this thing where the proofs (using the esbmc library) check the safety properties and the unit tests check the correctness so the state space doesn&amp;#x27;t explode and it takes a year to run the verification. Been working out pretty well so far (aside from spending more time tracking down esbmc bugs than working on my own code) and found some real issues, mostly integer overflow errors but other ones too. Kind of loosely based on the paper &amp;quot;A New Era in Software Security: Towards Self-Healing Software via Large Language Models and Formal Verification&amp;quot;…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2305.14752/"&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>
