<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Alex Useche on The Trail of Bits Blog</title><link>https://miscreants.github.io/blog.trailofbits.com/authors/alex-useche/</link><description>Recent content in Alex Useche on The Trail of Bits Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 08 Nov 2021 23:28:45 -0500</lastBuildDate><atom:link href="https://miscreants.github.io/blog.trailofbits.com/authors/alex-useche/index.xml" rel="self" type="application/rss+xml"/><item><title>Discovering goroutine leaks with Semgrep</title><link>https://miscreants.github.io/blog.trailofbits.com/2021/11/08/discovering-goroutine-leaks-with-semgrep/</link><pubDate>Mon, 08 Nov 2021 23:28:45 -0500</pubDate><guid>https://miscreants.github.io/blog.trailofbits.com/2021/11/08/discovering-goroutine-leaks-with-semgrep/</guid><description>Originally published May 10, 2021 While learning how to write multithreaded code in Java or C++ can make computer science students reconsider their career choices, calling a function asynchronously in Go is just a matter of prefixing a function call with the go keyword. However, writing concurrent Go code can […]</description></item></channel></rss>