Red Hat Bugzilla – Bug 1293447
[abrt] chordii: strcpy(): chordii killed by SIGSEGV
Last modified: 2016-12-20 12:17:50 EST
Version-Release number of selected component:
cmdline: chordii -t14 -s32 -g -p0 -i -
runlevel: N 5
Thread no. 1 (4 frames)
#1 strcpy at /usr/include/bits/string3.h:110
#2 tolower_str at common.c:34
#3 do_directive at chordii.c:900
#4 process_file at chordii.c:1168
Created attachment 1108396 [details]
Created attachment 1108397 [details]
Created attachment 1108398 [details]
Created attachment 1108399 [details]
Created attachment 1108400 [details]
Created attachment 1108401 [details]
Created attachment 1108402 [details]
Created attachment 1108403 [details]
Created attachment 1108404 [details]
Created attachment 1108405 [details]
Created attachment 1108406 [details]
Created attachment 1108407 [details]
Created attachment 1108408 [details]
Can you attach a copy of the input file that caused the crash?
(In reply to Johan Vromans from comment #14)
> Can you attach a copy of the input file that caused the crash?
The input file has been modified by an awk script, but I made many attempts and I cannot remember the version related to this crash. As I am just a beginner with awk, the awk script probably did something strange. However I will send you the input file, but if it happened to me only, I think we can ignore this crash.
Created attachment 1109050 [details]
*** Bug 1293450 has been marked as a duplicate of this bug. ***
*** Bug 1293452 has been marked as a duplicate of this bug. ***
Thanks for the input data. Unfortunately, I am not able to reproduce your crashes with this data.
Chordii's core has been programmed a long time ago, when robustness was not the most important requirement for its development. There are many situations that can result in crashes, most notably excessive long input lines and strings. However, this should still be rather exceptional and not an everyday experience.
If you encounter another crash please save the exact input data, verify that you can reproduce the crash with that data, and then attach it to this bug. If I can reproduce the crash I'll definitely fix it.
For convenience, I marked bugs 1293450 and 1293452 as duplicates of this one, since the underlying problem is the same.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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
Thank you for reporting this bug and we are sorry it could not be fixed.