Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 614590 - dev-vcs/tig-2.2.1: segfault
Summary: dev-vcs/tig-2.2.1: segfault
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Tim Harder
URL: https://github.com/jonas/tig/issues/568
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-04 00:46 UTC by Raymond Jennings
Modified: 2017-04-12 07:55 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
gdb backtrace (tigcrash,2.43 KB, application/octet-stream)
2017-04-04 00:47 UTC, Raymond Jennings 		Details
emerge --info (einfo.txt,5.69 KB, text/plain)
2017-04-04 00:47 UTC, Raymond Jennings 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Raymond Jennings 2017-04-04 00:46:34 UTC 
See attached
Comment 1 Raymond Jennings 2017-04-04 00:47:01 UTC 
Created attachment 469114 [details]
gdb backtrace
Comment 2 Raymond Jennings 2017-04-04 00:47:18 UTC 
Created attachment 469116 [details]
emerge --info
Comment 3 Raymond Jennings 2017-04-04 00:48:16 UTC 
Version numbers:

dev-vcs/tig-2.2.1::gentoo was built with the following:
USE="unicode" ABI_X86="64"

sys-libs/ncurses-5.9-r101::gentoo was built with the following:
USE="tinfo unicode -gpm" ABI_X86="32 64 -x32"

sys-libs/ncurses-6.0-r1::gentoo was built with the following:
USE="cxx threads tinfo unicode -ada -debug -doc -gpm -minimal -profile -static-libs -test -trace" ABI_X86="32 64 -x32"
Comment 4 Raymond Jennings 2017-04-04 10:56:07 UTC 
tig version 2.1.1 works fine.
Comment 5 Raymond Jennings 2017-04-09 17:56:43 UTC 
tig version 2.2 works fine as well.

For now I'd suggest readding version 2.2 back to the portage tree until the segfault in 2.2.1.
Comment 6 Tim Harder gentoo-dev 2017-04-09 19:45:28 UTC 
It would be nice to have more info here than a simple backtrace.

1. How are you triggering the segfault? For example, is it from simply opening tig against a repo or some certain key combo within tig on a repo?

2. Is it always reproducible under the same conditions against any repo?

3. Does the live ebuild also segfault in the same manner?
Comment 7 Raymond Jennings 2017-04-10 01:43:28 UTC 
Just typing "tig" by itself triggers the segfault, even against a live copy of the main dev tree for gentoo itself.

It appears to trigger against all repos.

I only noticed when 2.2.1 was stabilized.
Comment 8 Raymond Jennings 2017-04-10 02:30:46 UTC 
And yes, the live ebuild segfaults in the same manner as of yesterday.
Comment 9 Tim Harder gentoo-dev 2017-04-11 08:17:35 UTC 
I assume it's this bug, https://github.com/jonas/tig/issues/568.
Comment 10 Raymond Jennings 2017-04-12 02:12:31 UTC 
https://github.com/jonas/tig/pull/585

The 9999 version works as of now.
Comment 11 Tim Harder gentoo-dev 2017-04-12 07:55:56 UTC 
2.2.1-r1 now includes the relevant patch.