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
Created attachment 955470 [details] File: backtrace
Created attachment 955471 [details] File: cgroup
Created attachment 955472 [details] File: core_backtrace
Created attachment 955473 [details] File: dso_list
Created attachment 955474 [details] File: environ
Created attachment 955475 [details] File: exploitable
Created attachment 955476 [details] File: limits
Created attachment 955477 [details] File: maps
Created attachment 955478 [details] File: open_fds
Created attachment 955479 [details] File: proc_pid_status
Created attachment 955480 [details] File: var_log_messages
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.
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.
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.