Bug 682422

Summary: [abrt] virtuoso-opensource-6.1.2-1.fc14: __longjmp_chk: Process /usr/bin/virtuoso-t was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Malar Kannan <malarkannan.p>
Component: virtuoso-opensourceAssignee: Rex Dieter <rdieter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: pingou, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2797e51e92f6385dc03550443aa62916761dcf92
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 14:45:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Malar Kannan 2011-03-05 11:50:00 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 79156 bytes
cmdline: /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_kn8238.ini +wait
component: virtuoso-opensource
Attached file: coredump, 102866944 bytes
crash_function: __longjmp_chk
executable: /usr/bin/virtuoso-t
kernel: 2.6.35.11-83.fc14.x86_64
package: virtuoso-opensource-6.1.2-1.fc14
rating: 4
reason: Process /usr/bin/virtuoso-t was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299325624
uid: 501

How to reproduce
-----
1.I logged into different session with same user.
2.when i came back to first session.
3.it crashed
Comment 1 Malar Kannan 2011-03-05 11:50:09 UTC 
Created attachment 482430 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 14:45:13 UTC 
Backtrace analysis found this bug to be similar to bug #744471, closing as duplicate.

Bugs which were found to be similar to this bug: bug #593213, bug #744471

This comment is automatically generated.

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