Bug 1161935

Summary: [abrt] texlive-lacheck-bin: yylex(): lacheck killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Herman Grootaers <herman>
Component: texliveAssignee: Jindrich Novy <novyjindrich>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: herman, novyjindrich, pertusus, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9bd30112c225acd116565a67cc7df7ebfa26fe5b
Whiteboard: abrt_hash:aad1c13e42b2c46017a8368c2345c38feeb0cc2a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 23:13:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Herman Grootaers 2014-11-09 14:48:07 UTC
Description of problem:
Editing with vi a *tex-file of 41112  lines 929809 words and 6173483 characters. When I saved the file after a number of changes in the file vi seemed to have been crashed, but work seemed to be possible.

Version-Release number of selected component:
texlive-lacheck-bin-svn30088.0-5.20131226_r32488.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        lacheck Bijbel_EXPL3.tex
crash_function: yylex
executable:     /usr/bin/lacheck
kernel:         3.16.7-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (1 frames)
 #0 yylex at lacheck.l:254

Comment 1 Herman Grootaers 2014-11-09 14:48:11 UTC
Created attachment 955470 [details]
File: backtrace

Comment 2 Herman Grootaers 2014-11-09 14:48:12 UTC
Created attachment 955471 [details]
File: cgroup

Comment 3 Herman Grootaers 2014-11-09 14:48:13 UTC
Created attachment 955472 [details]
File: core_backtrace

Comment 4 Herman Grootaers 2014-11-09 14:48:15 UTC
Created attachment 955473 [details]
File: dso_list

Comment 5 Herman Grootaers 2014-11-09 14:48:16 UTC
Created attachment 955474 [details]
File: environ

Comment 6 Herman Grootaers 2014-11-09 14:48:17 UTC
Created attachment 955475 [details]
File: exploitable

Comment 7 Herman Grootaers 2014-11-09 14:48:18 UTC
Created attachment 955476 [details]
File: limits

Comment 8 Herman Grootaers 2014-11-09 14:48:19 UTC
Created attachment 955477 [details]
File: maps

Comment 9 Herman Grootaers 2014-11-09 14:48:20 UTC
Created attachment 955478 [details]
File: open_fds

Comment 10 Herman Grootaers 2014-11-09 14:48:22 UTC
Created attachment 955479 [details]
File: proc_pid_status

Comment 11 Herman Grootaers 2014-11-09 14:48:23 UTC
Created attachment 955480 [details]
File: var_log_messages

Comment 12 Herman Grootaers 2014-11-12 18:35:23 UTC
This bug also occurs when lacheck is called from vim; called from the GUI as open this file with...

vim continues to run, but it is annoying due to the fact that I need a lot of work to do on this file.

If necessary I can (and will) append the file as an attachment, but I prefer to send it to the maintainer directly.

Comment 13 Fedora End Of Life 2015-05-29 13:15:28 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Fedora End Of Life 2015-06-29 23:13:21 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.