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

Re: [PATCH v2] doc: hint about GIT_DEBUGGER

From
Elijah Newren <newren@gmail.com>
Date
May 21, 2019, 16:06 UTC
Message-ID
<CABPp-BHehO4dJCpNHws=PAaqxTyoeLyb3N1BGFG+AEEgBYVtBQ@mail.gmail.com>
In-Reply-To
<20190521010036.70378-1-emilyshaffer@google.com>
On Mon, May 20, 2019 at 6:01 PM Emily Shaffer <emilyshaffer@google.com> wrote:
Show 6 quoted lines
>
> 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).
>
Two very minor nits:
> It looks like you can use GIT_DEBUGGER to pick gdb by default, or you
I think it'd sound better without 'It looks like'; perhaps drop that part?
> can hand it your own debugger if you like to use something else (or if
> you want custom flags for gdb). Hopefully document that intent within
> CodingGuidelines.
Maybe just leave out 'Hopefully'?
Show 20 quoted lines
>
> 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..e99af36df9 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=my-debugger-binary my-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`.)
> +
Other than the minor nits above:
Acked-by: Elijah Newren <newren@gmail.com>
Previous: Emily ShafferNext: Emily Shaffer
Message 5 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.