`git log` crashes, quite regularly but always at a different output line
git log crashes for me, quite regularly but always at a different output line:
$ git --no-pager log commit 7ebe0c9833da54f781efe57daf11f15dbe405abf (HEAD -> master, origin/master, origin/HEAD) Segmentation fault $ git --no-pager log commit 7ebe0c9833da54f781efe57daf11f15dbe405abf (HEAD -> master, origin/master, origin/HEAD) Author: myauthor <email@example.com> Date: Sat Jul 4 14:24:28 2020 +0200 Tweaks to exception frame data structure commit 5f884593cf63245560b1059d2e39703b0f63ae1d Segmentation fault
I run it on the PinePhone UBPorts CE (HW rev. 1.2) with postmarketOS based on Alpine Edge.
Since there is no git-gdb (I asked for it here #11716 (closed) ) this is all I have as a backtrace for now:
#0 0x0000aaaaaabcb00c in ?? () #1 0x0000aaaaaabb8220 in ?? () #2 0x0000aaaaaabb8aa4 in ?? () #3 0x0000aaaaaab00f30 in ?? () #4 0x0000aaaaaab0182c in ?? () #5 0x0000aaaaaaac7b84 in ?? () #6 0x0000aaaaaaac888c in ?? () #7 0x0000aaaaaaac75ec in ?? () #8 0x0000fffff7f7077c in libc_start_main_stage2 (main=0xaaaaaaac7540, argc=2, argv=0xfffffffffb98) at src/env/__libc_start_main.c:94 #9 0x0000000000000000 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Once git-gdb becomes available I will happily update this.
(Note: this ticket was forwarded from https://gitlab.com/postmarketOS/pmaports/-/issues/667 where it was suggested filing it here might be better suited)