Bug 583982 - [abrt] crash in groff-1.18.1.4-20.fc13: Process /usr/bin/troff was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in groff-1.18.1.4-20.fc13: Process /usr/bin/troff was killed by ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: groff
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jan Vcelak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:01c38cb229ee1d9ad1d8437c945...
Depends On:
Blocks: 608794
TreeView+ depends on / blocked
 
Reported: 2010-04-20 12:52 UTC by Michal Hlavinka
Modified: 2013-03-04 01:27 UTC (History)
2 users (show)

Fixed In Version: groff-1.18.1.4-22.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 608794 (view as bug list)
Environment:
Last Closed: 2010-07-07 17:37:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (7.31 KB, text/plain)
2010-04-20 12:52 UTC, Michal Hlavinka
no flags Details

Description Michal Hlavinka 2010-04-20 12:52:53 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: troff -mtty-char -man -Tutf8
component: groff
executable: /usr/bin/troff
global_uuid: 01c38cb229ee1d9ad1d8437c9453178daa6f56e7
kernel: 2.6.33.2-56.fc13.x86_64
package: groff-1.18.1.4-20.fc13
rating: 4
reason: Process /usr/bin/troff was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.wget http://philipp.fedorapeople.org/cyrus-imapd-2.3.16-3.fc12.src.rpm -O cyrus-imapd-2.3.16-3.fc12.src.rpm.1
2.mc
3.navigate to that file, hit enter
4.press 'q'

->crash

Comment 1 Michal Hlavinka 2010-04-20 12:52:55 UTC
Created attachment 407811 [details]
File: backtrace

Comment 2 Jan Vcelak 2010-06-28 11:02:40 UTC
I don't manage to reproduce the segfault.

In addition, I think that opening binary file as a manual page is not a good idea. 'mc' should recognize the file type from its content, not from its extension. This is not a problem of groff.

Comment 3 Michal Hlavinka 2010-06-28 12:33:16 UTC
(In reply to comment #2)
> I don't manage to reproduce the segfault.

dd if=/dev/urandom of=test.1 bs=1M count=10
mc
navigate to test.1
hit enter
press 'q'
->crash

if you can't generate test.1 that "works" (all I've generated were able to reproduce this problem) I can upload a working one somewhere

> In addition, I think that opening binary file as a manual page is not a good
> idea.

agree

> 'mc' should recognize the file type from its content, not from its
> extension.

yes, that would be much better

> This is not a problem of groff.    

disagree. Any error message would be fine/expected, but sigsegv is definitely wrong behaviour

Comment 5 Jan Vcelak 2010-06-28 17:03:58 UTC
That was really tricky! It depends on LC_ALL setting.

With LC_ALL=C, I get SIGSEGV.
With my default LC_ALL=cs_CZ.utf8, I get SIGABRT.

Both are different bugs. The first one is already fixed in upstream. The second one is not yet, however I've working patch.

Thank you for reopening. ;)

Jan

Comment 6 Fedora Update System 2010-06-28 17:56:59 UTC
groff-1.18.1.4-22.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/groff-1.18.1.4-22.fc13

Comment 7 Fedora Update System 2010-06-28 17:59:03 UTC
groff-1.18.1.4-22.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/groff-1.18.1.4-22.fc12

Comment 8 Fedora Update System 2010-06-28 23:38:08 UTC
groff-1.18.1.4-22.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update groff'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/groff-1.18.1.4-22.fc13

Comment 9 Fedora Update System 2010-07-07 17:37:30 UTC
groff-1.18.1.4-22.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2010-08-17 05:32:20 UTC
groff-1.18.1.4-22.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.