git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v4] doc: hint about GIT_DEBUGGER in CodingGuidelines

From
Emily Shaffer <emilyshaffer@google.com>
Date
May 28, 2019, 19:07 UTC
Message-ID
<20190528190729.78029-1-emilyshaffer@google.com>
In-Reply-To
<20190523005533.260611-1-emilyshaffer@google.com>

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>
---
 Documentation/CodingGuidelines | 6 ++++++
 1 file changed, 6 insertions(+)
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
index 32210a4386..1169ff6c8e 100644
--- a/Documentation/CodingGuidelines
+++ b/Documentation/CodingGuidelines
@@ -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.
 
+ - 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.
-- 
2.22.0.rc1.257.g3120a18244-goog
Previous: Emily Shaffer
Message 10 of 10 in “doc: hint about GIT_DEBUGGER”
  1. doc: hint about GIT_DEBUGGEREmily Shaffer, May 17, 2019
  2. Elijah NewrenMay 18, 2019
  3. Emily ShafferMay 20, 2019
  4. doc: hint about GIT_DEBUGGEREmily Shaffer, May 21, 2019
  5. Elijah NewrenMay 21, 2019
  6. Emily ShafferMay 21, 2019
  7. doc: hint about GIT_DEBUGGER in CodingGuidelinesEmily Shaffer, May 23, 2019
  8. Eric SunshineMay 23, 2019
  9. Emily ShafferMay 28, 2019
  10. doc: hint about GIT_DEBUGGER in CodingGuidelinesEmily Shaffer, May 28, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.