<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Pypy on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/pypy/</link><description>Recent content in Pypy on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Sun, 11 Sep 2016 14:06:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/pypy/index.xml" rel="self" type="application/rss+xml"/><item><title>Reverse debugging for Python</title><link>http://karpoke.ignaciocano.com/2016/09/11/reverse-debugging-for-python/</link><pubDate>Sun, 11 Sep 2016 14:06:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2016/09/11/reverse-debugging-for-python/</guid><description>&lt;blockquote&gt;
&lt;p&gt;A ”reverse debugger” is a debugger where you can go forward and backward in
time. It is an uncommon feature, at least in the open source world, but I
have no idea why. I have used undodb-gdb and rr, which are reverse debuggers
for C code, and I can only say that they saved me many, many days of poking
around blindly in gdb.&lt;/p&gt;
&lt;p&gt;The PyPy team is pleased to give you ”RevPDB”, a reverse-debugger similar to
rr but for Python.&lt;/p&gt;
&lt;/blockquote&gt;</description></item></channel></rss>