gitg crashes with SIGSEG, repeatable

Bug #2025693 reported by psl
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gitg (Ubuntu)
Fix Released
Undecided
Unassigned
Focal
Confirmed
Undecided
Unassigned
Jammy
Confirmed
Undecided
Unassigned

Bug Description

gitg 3.32.1-1
Linux Mint 20.3 Una amd64

gitg crashes with coredump, it is repeatable

How to repeat:

user@ubuntu:~$ gitg -v
gitg 3.32.1

user@ubuntu:~$ git clone git://git.ipfire.org/ipfire-2.x.git
user@ubuntu:~$ cd ipfire-2.x

user@ubuntu:~/ipfire-2.x$ gdb gitg
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04.1) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gitg...
(No debugging symbols found in gitg)
(gdb) run
Starting program: /usr/bin/gitg
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff291b700 (LWP 91480)]
[New Thread 0x7ffff211a700 (LWP 91481)]
[New Thread 0x7ffff1876700 (LWP 91482)]
[New Thread 0x7ffff0ea3700 (LWP 91483)]
[New Thread 0x7fffdb680700 (LWP 91484)]
[New Thread 0x7fffdae7f700 (LWP 91485)]
[New Thread 0x7fffda67e700 (LWP 91486)]
[Thread 0x7fffda67e700 (LWP 91486) exited]
[Thread 0x7fffdae7f700 (LWP 91485) exited]
[Thread 0x7fffdb680700 (LWP 91484) exited]
[Thread 0x7ffff0ea3700 (LWP 91483) exited]
[New Thread 0x7ffff0ea3700 (LWP 91495)]
[New Thread 0x7fffdae7f700 (LWP 91496)]
[Thread 0x7ffff0ea3700 (LWP 91495) exited]

Thread 1 "gitg" received signal SIGSEGV, Segmentation fault.
0x00007ffff6776751 in ?? () from /lib/x86_64-linux-gnu/libpcre.so.3

---

It crash when I try to view commit 579c5830aa99b4f2d67e5ac7d8688babe8b3caee

user@ubuntu:~/ipfire-2.x$ git log 579c5830aa99b4f2d67e5ac7d8688babe8b3caee | head -6
commit 579c5830aa99b4f2d67e5ac7d8688babe8b3caee
Author: Adolf Belka <email address hidden>
Date: Fri May 19 13:47:47 2023 +0200

    curl: Update to version 8.1.0

---

no crash with git but gitg cannot process it and crashes... :-(

user@ubuntu:~/ipfire-2.x$ gitg
Segmentation fault (core dumped)

Tags: focal jammy
Revision history for this message
Sudip Mukherjee (sudipmuk) wrote :

I have tested and confirmed that the issue can be reproduced on Jammy and Focal. Also tested and confirmed that the other releases are not affected.

tags: added: focal jammy
Changed in gitg (Ubuntu):
status: New → Fix Released
Changed in gitg (Ubuntu Focal):
status: New → Confirmed
Changed in gitg (Ubuntu Jammy):
status: New → Confirmed
Revision history for this message
Sudip Mukherjee (sudipmuk) wrote :

The steps to reproduce the bug on Focal or Jammy:

git clone git://git.ipfire.org/ipfire-2.x.git
cd ipfire-2.x
git reset --hard 579c5830aa99b4f2d67e5ac7d8688babe8b3caee
gitg

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.