Bug 647150 - [abrt] gettext-0.18.1.1-4.fc14: qsort_r: Process /usr/bin/msgmerge was killed by signal 8 (SIGFPE)
Summary: [abrt] gettext-0.18.1.1-4.fc14: qsort_r: Process /usr/bin/msgmerge was killed...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gettext
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:17d06bc1d465f8ac6bc8b83f543...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-27 11:52 UTC by Richard W.M. Jones
Modified: 2010-11-01 02:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-01 02:21:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (29.50 KB, text/plain)
2010-10-27 11:52 UTC, Richard W.M. Jones
no flags Details

Description Richard W.M. Jones 2010-10-27 11:52:39 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: msgmerge hi.po libguestfs.pot -o /home/rjones/d/libguestfs/po/hi.new.po
component: gettext
crash_function: qsort_r
executable: /usr/bin/msgmerge
kernel: 2.6.35.6-46.fc14.x86_64
package: gettext-0.18.1.1-4.fc14
rating: 4
reason: Process /usr/bin/msgmerge was killed by signal 8 (SIGFPE)
release: Fedora release 14 (Laughlin)
time: 1288180209
uid: 500

How to reproduce
-----
1. Running 'make dist' in libguestfs source directory.
2.
3.

Comment 1 Richard W.M. Jones 2010-10-27 11:52:42 UTC
Created attachment 455957 [details]
File: backtrace

Comment 2 Jens Petersen 2010-10-28 02:36:40 UTC
Do you have gettext-debuginfo installed?

Could you please provide complete steps to reproduce?

I wonder if this is related to bug 628073.

Comment 3 Richard W.M. Jones 2010-10-28 07:54:38 UTC
This is now not happening for me.  I'll see if it
reoccurs next time we do a release.

Comment 4 Jens Petersen 2010-11-01 02:21:28 UTC
Ok thanks - np - let me close it for now, please
reopen if you see it again.


Note You need to log in before you can comment on or make changes to this bug.