From 39e44d7a9c7fea5e6e8f343082f8f28c4576d5e4 Mon Sep 17 00:00:00 2001
From: Barry Warsaw <barry@python.org>
Date: Tue, 23 Jan 2001 16:25:19 +0000
Subject: [PATCH] A few useful definitions if you're using gdb.  Copy to
 ~/.gdbinit to pull it in automatically.

---
 Misc/gdbinit | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 Misc/gdbinit

diff --git a/Misc/gdbinit b/Misc/gdbinit
new file mode 100644
index 00000000000..a164f4266c3
--- /dev/null
+++ b/Misc/gdbinit
@@ -0,0 +1,27 @@
+# -*- ksh -*-
+#
+# If you use the GNU debugger gdb to debug the Python C runtime, you
+# might find some of the following commands useful.  Copy this to your
+# ~/.gdbinit file and it'll get loaded into gdb automatically when you
+# start it up.  Then, at the gdb prompt you can do things like:
+#
+#    (gdb) pyo apyobjectptr
+#    <module 'foobar' (built-in)>
+#    refcounts: 1
+#    address    : 84a7a2c
+#    $1 = void
+#    (gdb)
+
+# Prints a representation of the object to stderr, along with the
+# number of reference counts it current has and the hex address the
+# object is allocated at.  The argument must be a PyObject*
+define pyo
+print PyObject_Dump($arg0)
+end
+
+# Prints a representation of the object to stderr, along with the
+# number of reference counts it current has and the hex address the
+# object is allocated at.  The argument must be a PyGC_Head*
+define pyg
+print PyGC_Dump($arg0)
+end