diff --git a/docs/linux_debugging_gtk.md b/docs/linux_debugging_gtk.md
new file mode 100644
index 0000000..93a1afb1
--- /dev/null
+++ b/docs/linux_debugging_gtk.md
@@ -0,0 +1,51 @@
+## Making warnings fatal
+
+See [Running GLib Applications](http://developer.gnome.org/glib/stable/glib-running.html) for notes on how to make GTK warnings fatal.
+
+## Using GTK Debug packages
+
+```
+sudo apt-get install libgtk2.0-0-dbg
+```
+Make sure that you're building a binary that matches your architecture (e.g. 64-bit on a 64-bit machine), and there you go.
+
+### Source
+You'll likely want to get the source for gtk too so that you can step through it.  You can tell gdb that you've downloaded the source to your system's GTK by doing:
+
+```
+$ cd /my/dir
+$ apt-get source libgtk2.0-0
+$ gdb ...
+(gdb) set substitute-path /build/buildd /my/dir
+```
+
+NOTE: I tried debugging pango in a similar manner, but for some reason gdb didn't pick up the symbols from the symbols from the -dbg package. I ended up building from source and setting my LD\_LIBRARY\_PATH.
+
+See LinuxBuildingDebugGtk for more on how to build your own debug version of GTK.
+
+## Parasite
+http://chipx86.github.com/gtkparasite/ is great.  Go check out the site for more about it.
+
+Install it with
+```
+sudo apt-get install gtkparasite
+```
+
+And then run Chrome with
+```
+GTK_MODULES=gtkparasite ./out/Debug/chrome
+```
+
+### ghardy
+If you're within the Google network on ghardy, which is too old to include gtkparasite, you can do:
+```
+scp bunny.sfo:/usr/lib/gtk-2.0/modules/libgtkparasite.so /tmp
+sudo cp /tmp/libgtkparasite.so /usr/lib/gtk-2.0/modules/libgtkparasite.so
+```
+
+## GDK\_DEBUG
+
+```
+14:43 < xan> mrobinson: there's a way to run GTK+ without grabs fwiw, useful for gdb sessions
+14:44 < xan> GDK_DEBUG=nograbs
+```
\ No newline at end of file