Document all sorts of C debugging tips

[timholy]

Fulfills a pledge I made on on julia-dev. This moves some info I wrote from the FAQ to the "developer docs", and blatantly steals from sources posted by @ihnorton and @staticfloat. Finally, there's a small number of whitespace changes.

[ihnorton]

FWIW, I usually start julia directly under gdb. I think the only time I have used separate processes is when running julia under valgrind. (perhaps it is a matter of taste though?)

[staticfloat]

Me as well.

[timholy]

What's funny is that I'd swear Ctrl-C did not interrupt to gdb when I first tried it oh-so-long ago. So that's why I figured this out.

I'll change this (probably just delete the whole section).

[staticfloat]

It might be because of the new REPL.
On Nov 13, 2014 12:19 PM, "Tim Holy" [email protected] wrote:

In doc/devdocs/interactivegdb.rst:

@@ -0,0 +1,68 @@
+Interactive debugging with gdb
+----------------------------------
+
+First, you should build the debug version of julia with make +debug. Below, lines starting with (gdb) mean things you should
+type at the gdb prompt.
+
+From the shell
+^^^^^^^^^^^^^^
+
+The main challenge is that Julia and gdb each need to have their own
+terminal, to allow you to interact with them both. One approach is to

What's funny is that I'd swear Ctrl-C did not interrupt to gdb when I
first tried it oh-so-long ago. So that's why I figured this out.

I'll change this (probably just delete the whole section).

—
Reply to this email directly or view it on GitHub
https://github.com/JuliaLang/julia/pull/9000/files#r20319864.

[ihnorton]

Awesome 👍

[staticfloat]

:D

[staticfloat]

What does the scouter say about our PR level?!

[timholy]

@JuliaBackports

[tkelman]

thanks @timholy - what's the right conflict resolution for

  .. toctree::
-    :maxdepth: 1
+    :maxdepth: 2

++<<<<<<< HEAD
 +   devdocs/cartesian
++=======
+    devdocs/julia
+    devdocs/C
++>>>>>>> cbb4bc3... Document all sorts of C debugging tips

[timholy]

Pick the second one. Surprised there was a conflict...

Thanks for doing it!

[tkelman]

No problem, backported in 507a4c6

I think the conflict might be because devdocs/meta was not backported?