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

Segfault in the attr stack

From
Stefan Beller <sbeller@google.com>
Date
Jun 1, 2016, 22:00 UTC
Message-ID
<CAGZ79ka_4vZfNhgOyMeFKdossO-S5Q7RVnvEzB8YAJNc1YQ+uQ@mail.gmail.com>
(running git-next)
In the Gerrit repo I did
    $ echo "/plugins/commit-message-length-validator sub-default"
>>.gitattributes
    $ git status ":(attr:sub-default)"
Segmentation fault (core dumped)

Running this multiple times through gdb, this produces different back traces as it seems that threads are involved? (So I don't attach a back trace here)

Also notable are: *** Error in `/usr/local/google/home/sbeller/bin/git': double free or corruption (fasttop): 0x00007fffd80008f0 *** *** Error in `/usr/local/google/home/sbeller/bin/git': double free or corruption (fasttop): 0x00007ffff0001000 ***

When running another command `git status ":(attr:asdf)"`, I get git: attr.c:634: prepare_attr_stack: Assertion `attr_stack->origin' failed. git: attr.c:634: prepare_attr_stack: Assertion `attr_stack->origin' failed. git: attr.c:634: prepare_attr_stack: Assertion `attr_stack->origin' failed. git: attr.c:634: prepare_attr_stack: Assertion `attr_stack->origin' failed. Aborted (core dumped)

The failing assertions are an indication that sb/pathspec-label is using the attrs incorrectly or jc/attr added tighter assertions than I was aware of.

Stefan
Next: Junio C Hamano
Message 1 of 12 in “Segfault in the attr stack”
  1. Stefan BellerJun 1, 2016
  2. Junio C HamanoJun 1, 2016
  3. Stefan BellerJun 1, 2016
  4. Junio C HamanoJun 1, 2016
  5. Stefan BellerJun 1, 2016
  6. Junio C HamanoJun 1, 2016
  7. Junio C HamanoJun 1, 2016
  8. Junio C HamanoJun 2, 2016
  9. Junio C HamanoJun 2, 2016
  10. Stefan BellerJun 2, 2016
  11. Duy NguyenJun 2, 2016
  12. Duy NguyenJun 2, 2016

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.