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

Re: [Git 2.13.0] BUG: setup_git_env called without repository

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
May 12, 2017, 14:48 UTC
Message-ID
<alpine.DEB.2.21.1.1705121643180.146734@virtualbox>
In-Reply-To
<CANuW5x0pBwfQeha50mxN8pVQKm67u_b3UKTCQ8ZbJA6FUGvYbw@mail.gmail.com>
Hi Josh,
On Fri, 12 May 2017, Josh Hagins wrote:
Show 21 quoted lines
> Since upgrading to Git 2.13.0 I'm seeing this error message whenever
> `git config --local <whatever>` is called outside a Git repository.
> For example, note the difference in behavior between Git 2.13 and
> Apple Git:
> 
>     $ pwd
>     /Users/jhagins
>     $ /usr/bin/git --version
>     git version 2.11.0 (Apple Git-81)
>     $ /usr/bin/git config --local --get user.name
>     $ /usr/local/bin/git --version
>     git version 2.13.0
>     $ /usr/local/bin/git config --local --get user.name
>     fatal: BUG: setup_git_env called without repository
> 
> Apple Git outputs nothing, as expected. The summarized release notes
> published by GitHub specifically mentioned that instances of this
> error message should be reported, so here you go!
> 
> Please let me know if I can provide any more information that would be
> helpful.
Since this is in /usr/local/bin/, there are two possibilities:
1) you built and installed it yourself (but then it would be more likely
   in your $HOME/bin), or
2) you installed it via HomeBrew.
I guess it is the latter.

In both cases, however, you have XCode installed, so you can dig further. Yay.

The thing I would do in your case would be to clone Git:
	git clone https://github.com/git/git
then check out v2.13.0:
	git checkout v2.13.0

then edit the Makefile to remove the -O2 from the CFLAGS (the next step is to use the GNU debugger, and in my hands the -O2 optimization made that pretty useless), and then build with

	make

After that, you should be able to start the command in your local GNU debugger:

	gdb -args ./git config --local --get user.name
You will then want to set a breakpoint on the die_builtin() function:
	b die_builtin

Now run it with the `r` command, and it should stop in the die_builtin routine, in which case a backtrace would be most helpful to figure out what is going wrong:

	bt

If the output is not enlightening on its own, it would be nice to paste it into a reply to this mail so that the entire Git developer community can have a look.

Ciao, Johannes

Previous: Josh HaginsNext: Josh Hagins
Message 2 of 25 in “[Git 2.13.0] BUG: setup_git_env called without repository”
  1. Josh HaginsMay 12, 2017
  2. Johannes SchindelinMay 12, 2017
  3. Josh HaginsMay 15, 2017
  4. config: complain about --local outside of a git repoJeff King, May 12, 2017
  5. Ævar Arnfjörð BjarmasonMay 12, 2017
  6. Jeff KingMay 13, 2017
  7. 0/3 BUG() and "config --local" outside of repoJeff King, May 13, 2017
  8. 1/3 usage.c: add BUG() functionJeff King, May 13, 2017
  9. Jeff KingMay 13, 2017
  10. Junio C HamanoMay 15, 2017
  11. 2/3 setup_git_env: convert die("BUG") to BUG()Jeff King, May 13, 2017
  12. 3/3 config: complain about --local outside of a git repoJeff King, May 13, 2017
  13. 0/4 Finish the conversion from die("BUG: ...") to BUG()Johannes Schindelin, May 2, 2018
  14. 1/4 test-tool: help verifying BUG() code pathsJohannes Schindelin, May 2, 2018
  15. Duy NguyenMay 2, 2018
  16. Johannes SchindelinMay 5, 2018
  17. 2/4 run-command: use BUG() to report bugs, not die()Johannes Schindelin, May 2, 2018
  18. Jeff KingMay 7, 2018
  19. 3/4 Replace all die("BUG: ...") calls by BUG() onesJohannes Schindelin, May 2, 2018
  20. 4/4 Convert remaining die*(BUG) messagesJohannes Schindelin, May 2, 2018
  21. Jeff KingMay 7, 2018
  22. Jonathan NiederMay 13, 2017
  23. Jeff KingMay 13, 2017
  24. Josh HaginsMay 15, 2017
  25. Jeff KingMay 15, 2017

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.