Bug 604635 - [abrt] crash in crypto-utils-2.4.1-26: Perl_sv_clear: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in crypto-utils-2.4.1-26: Perl_sv_clear: Process /usr/bin/perl w...
Keywords:
Status: CLOSED DUPLICATE of bug 598160
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Newt
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Joe Orton
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7e6c41c96a8b093d53f72eeeae5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-16 11:44 UTC by François Kooman
Modified: 2010-10-14 13:12 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-10-14 13:12:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (32.69 KB, text/plain)
2010-06-16 11:45 UTC, François Kooman
no flags Details

Description François Kooman 2010-06-16 11:44:19 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/perl /usr/bin/genkey www.test.com
component: crypto-utils
crash_function: Perl_sv_clear
executable: /usr/bin/perl
global_uuid: 7e6c41c96a8b093d53f72eeeae5ac61bee04212d
kernel: 2.6.33.5-112.fc13.x86_64
package: crypto-utils-2.4.1-26
rating: 4
reason: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. genkey www.test.com
2.
3.

Comment 1 François Kooman 2010-06-16 11:45:11 UTC
Created attachment 424415 [details]
File: backtrace

Comment 2 François Kooman 2010-06-16 11:45:33 UTC
Package: crypto-utils-2.4.1-26
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. genkey www.test.com
2.
3.

Comment 3 Elio Maldonado Batiz 2010-06-16 13:35:40 UTC
This is a be a duplicate  of Bug 600670
See the attachment where I can reproduce it with what amounts to a 'hello world' perl script.

Comment 4 Joe Orton 2010-10-14 13:12:17 UTC

*** This bug has been marked as a duplicate of bug 598160 ***


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