Re: [Outreachy PATCH v6 1/3] environment: stop storing `core.attributesFile` globally
- From
- Phillip Wood <phillip.wood123@gmail.com>
- Date
- Feb 10, 2026, 15:07 UTC
- Message-ID
- <0a45d72a-2a11-4363-ad2b-9fabff70bc9f@gmail.com>
- In-Reply-To
- <aYsEpvFwCSHb5DYO@ubuntu>
On 10/02/2026 10:17, Bello Caleb Olamide wrote:
Show 7 quoted lines
> Initialized empty Git repository in /home/ubuntu/Code/open_source/git/t/trash directory.t4027-diff-submodule/sub/.git/ > [master (root-commit) 4431e0b] submodule > Author: A U Thor <author@example.com> > 1 file changed, 1 insertion(+) > create mode 100644 world > BUG: repository.c:56: trying to read config from wrong repository instance > Aborted (core dumped)
What does the backtrace show if you load the coredump into gdb? If you're using systemd you should be able to run
coredumpctl gdb
to start gdb on the last coredump (you can list them with "coredumpctl list" if you need to select a different one) and then you can run
bt full
in gdb to get a backtrace.
If you have an actual coredump file then you can just run "gdb path/to/coredump"
Thanks
Phillip
Show 32 quoted lines
> not ok 1 - setup > # > # test_tick && > # test_create_repo sub && > # ( > # cd sub && > # echo hello >world && > # git add world && > # git commit -m submodule > # ) && > # > # test_tick && > # echo frotz >nitfol && > # git add nitfol sub && > # git commit -m superproject && > # > # ( > # cd sub && > # echo goodbye >world && > # git add world && > # git commit -m "submodule #2" > # ) && > # > # git -C sub rev-list HEAD >revs && > # set x $(cat revs) && > # echo ":160000 160000 $3 $ZERO_OID M sub" >expect && > # subtip=$3 subprev=$2 > # > 1..1 > > Thanks >