doc: hint about GIT_DEBUGGER in CodingGuidelines
authorEmily Shaffer <emilyshaffer@google.com>
Tue, 28 May 2019 19:07:29 +0000 (12:07 -0700)
committerJunio C Hamano <gitster@pobox.com>
Tue, 28 May 2019 20:42:33 +0000 (13:42 -0700)
We check for a handy environment variable GIT_DEBUGGER when running via
bin-wrappers/, but this feature is undocumented. Add a hint to how to
use it into the CodingGuidelines (which is where other useful
environment settings like DEVELOPER are documented).

Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/CodingGuidelines
index 8579530710a7e2b665941be45264429b99d5134b..d67a35ad5d99baa2399db317e71fc1253f8c4ef5 100644 (file)
@@ -412,6 +412,12 @@ For C programs:
    must be declared with "extern" in header files. However, function
    declarations should not use "extern", as that is already the default.
 
    must be declared with "extern" in header files. However, function
    declarations should not use "extern", as that is already the default.
 
+ - You can launch gdb around your program using the shorthand GIT_DEBUGGER.
+   Run `GIT_DEBUGGER=1 ./bin-wrappers/git foo` to simply use gdb as is, or
+   run `GIT_DEBUGGER="<debugger> <debugger-args>" ./bin-wrappers/git foo` to
+   use your own debugger and arguments. Example: `GIT_DEBUGGER="ddd --gdb"
+   ./bin-wrappers/git log` (See `wrap-for-bin.sh`.)
+
 For Perl programs:
 
  - Most of the C guidelines above apply.
 For Perl programs:
 
  - Most of the C guidelines above apply.