Bug 619729 - [abrt] crash in virtuoso-opensource-6.1.1-1.fc13: gpf_notice: Process /usr/bin/virtuoso-t was killed by signal 11 (SIGSEGV)
[abrt] crash in virtuoso-opensource-6.1.1-1.fc13: gpf_notice: Process /usr/bi...
Status: CLOSED DUPLICATE of bug 613913
Product: Fedora
Classification: Fedora
Component: virtuoso-opensource (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Rex Dieter
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-07-30 06:41 EDT by John Kissane
Modified: 2010-11-09 08:43 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 08:43:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (16.67 KB, text/plain)
2010-07-30 06:41 EDT, John Kissane
no flags Details

  None (edit)
Description John Kissane 2010-07-30 06:41:37 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_h24034.ini +wait
component: virtuoso-opensource
crash_function: gpf_notice
executable: /usr/bin/virtuoso-t
global_uuid: 3ec98c27513d6d528bcd190be08a11b9e4d73602
package: virtuoso-opensource-6.1.1-1.fc13
rating: 4
reason: Process /usr/bin/virtuoso-t was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
1. Don't know as I'm not sure what virtuoso actually does!
Comment 1 John Kissane 2010-07-30 06:41:39 EDT
Created attachment 435524 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 08:43:42 EST

*** This bug has been marked as a duplicate of bug 613913 ***
Comment 3 Karel Klíč 2010-11-09 08:43:42 EST
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #613913.

Sorry for the inconvenience.

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