<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Akshay Kumar on The Trail of Bits Blog</title><link>https://miscreants.github.io/blog.trailofbits.com/authors/akshay-kumar/</link><description>Recent content in Akshay Kumar on The Trail of Bits Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 21 Jan 2019 07:50:27 -0500</lastBuildDate><atom:link href="https://miscreants.github.io/blog.trailofbits.com/authors/akshay-kumar/index.xml" rel="self" type="application/rss+xml"/><item><title>How McSema Handles C++ Exceptions</title><link>https://miscreants.github.io/blog.trailofbits.com/2019/01/21/how-mcsema-handles-c-exceptions/</link><pubDate>Mon, 21 Jan 2019 07:50:27 -0500</pubDate><guid>https://miscreants.github.io/blog.trailofbits.com/2019/01/21/how-mcsema-handles-c-exceptions/</guid><description>C++ programs using exceptions are problematic for binary lifters. The non-local control-flow “throw” and “catch” operations that appear in C++ source code do not map neatly to straightforward binary representations. One could allege that the compiler, runtime, and stack unwinding library collude to make exceptions work. We recently completed our investigation into exceptions and can […]</description></item></channel></rss>