Author: Carl Friedrich Bolz <[email protected]>
Branch: extradoc
Changeset: r5646:0b3db1b1698e
Date: 2016-07-06 15:33 +0200
http://bitbucket.org/pypy/extradoc/changeset/0b3db1b1698e/
Log: - linkify the commit
- I didn't understand something
diff --git a/blog/draft/revdb.rst b/blog/draft/revdb.rst
--- a/blog/draft/revdb.rst
+++ b/blog/draft/revdb.rst
@@ -49,9 +49,11 @@
Right now, RevDB works barely enough to start being useful. I have
used it to track one real bug (for the interested people, see
-bd220c268bc9). So here is what it is, what it is not, and how to use
+bd220c268bc9_). So here is what it is, what it is not, and how to use
it.
+.. _bd220c268bc9: https://bitbucket.org/pypy/pypy/commits/bd220c268bc9
+
RevDB is a Python debugger. It will not help track issues like
segfaults or crashes of the interpreter, but it will help track any
Python-level bugs. Think about bugs that end up as a Python traceback
@@ -79,6 +81,9 @@
backwards. Most importantly, you can set *watchpoints*. More about
that later.
+
+XXX CF: it's not clear to me what "doing any input/output from the debugger"
means
+
What you cannot do is do any input/output from the debugger. Indeed,
the log file records all imports that were done and what the imported
modules contained. Running the debugger on the log file gives an
_______________________________________________
pypy-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-commit
