Version-Release number of selected component: man-db-2.6.5-4.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: mandb -q crash_function: xrealloc executable: /usr/bin/mandb kernel: 3.16.2-201.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #2 xrealloc at xmalloc.c:61 #3 get_block at pipeline.c:2116 #4 get_line at pipeline.c:2181 #5 pipeline_readline at pipeline.c:2205 #6 ult_src at ult_src.c:384 #7 test_manfile at check_mandirs.c:240 #8 add_dir_entries at check_mandirs.c:346 #9 testmandirs at check_mandirs.c:517 #10 create_db at check_mandirs.c:604 #11 update_db_wrapper at mandb.c:367
Created attachment 939745 [details] File: backtrace
Created attachment 939746 [details] File: cgroup
Created attachment 939747 [details] File: core_backtrace
Created attachment 939748 [details] File: dso_list
Created attachment 939749 [details] File: environ
Created attachment 939750 [details] File: exploitable
Created attachment 939751 [details] File: limits
Created attachment 939752 [details] File: maps
Created attachment 939753 [details] File: open_fds
Created attachment 939754 [details] File: proc_pid_status
Created attachment 939755 [details] File: var_log_messages
The only way to be sure would be to rerun under valgrind and reproduce the problem there, which would locate the problem much more accurately (this type of failure only causes the program to crash some time after things actually went wrong); but the bug I fixed in http://git.savannah.gnu.org/cgit/libpipeline.git/commit/?id=6ade4a2d378b29332ab51d90d6b3caae08824f31 is a possibility.
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.