Description of problem: use ru_RU/pgadmin3.po as testcase. program craches when try to save it Version-Release number of selected component: poedit-1.4.6.1-5.fc17 Additional info: libreport version: 2.0.13 abrt_version: 2.0.12 backtrace_rating: 4 cmdline: poedit pgadmin3.po crash_function: __memmove_ssse3_back kernel: 3.5.2-3.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 __memmove_ssse3_back at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S : #1 memmove at /usr/include/bits/string3.h : #2 __db_pitem_nolog at ../../db/db_dup.c : #3 __db_pitem at ../../db/db_dup.c : #4 __bam_iitem at ../../btree/bt_put.c : #5 __ram_add at ../../btree/bt_recno.c : #6 __ram_append at ../../btree/bt_recno.c : #7 __db_put at ../../db/db_am.c : #8 __db_put_pp at ../../db/db_iface.c : #9 DbTrans::Write at transmem.cpp
Created attachment 610626 [details] File: core_backtrace
Created attachment 610627 [details] File: environ
Created attachment 610628 [details] File: backtrace
Created attachment 610629 [details] File: limits
Created attachment 610630 [details] File: cgroup
Created attachment 610631 [details] File: maps
Created attachment 610632 [details] File: dso_list
Created attachment 610633 [details] File: var_log_messages
Created attachment 610634 [details] File: open_fds
poedit-1.5.4-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/poedit-1.5.4-1.fc18
Package poedit-1.5.4-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing poedit-1.5.4-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15998/poedit-1.5.4-1.fc18 then log in and leave karma (feedback).
Created attachment 629284 [details] stack trace
I built poedit-1.5.4-3.fc18.src.rpm on my f17 linux box and catch this fault again Program received signal SIGSEGV, Segmentation fault. __memmove_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1579 1579 movdqu -16(%rsi), %xmm0
Can you please attach the offending po file?
Created attachment 629317 [details] pgadmin3.po RU
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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.
Please update to latest version and see if still happen as well, otherwise I will close this.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
(In reply to Christopher Meng from comment #17) > Please update to latest version and see if still happen as well, otherwise I > will close this. poedit-1.5.4-6.fc19.x86_64 still crashes
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.