Bug 620357 - [abrt] crash in rapidsvn-0.12.0-1.fc13: raise: Process /usr/bin/rapidsvn was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in rapidsvn-0.12.0-1.fc13: raise: Process /usr/bin/rapidsvn was ...
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: rapidsvn (Show other bugs)
(Show other bugs)
Version: 13
Hardware: x86_64 Linux
low
medium
Target Milestone: ---
Assignee: Tim Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d1f189a4ceee35a6724f61046e5...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-02 10:05 UTC by Giuliano Catrambone
Modified: 2010-09-11 13:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-09-11 13:48:36 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (41.29 KB, text/plain)
2010-08-02 10:05 UTC, Giuliano Catrambone 		no flags Details
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
RapidSVN 720 None None None Never

Description Giuliano Catrambone 2010-08-02 10:05:13 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: rapidsvn
component: rapidsvn
crash_function: raise
executable: /usr/bin/rapidsvn
global_uuid: d1f189a4ceee35a6724f61046e5d5199c8a2d7e3
kernel: 2.6.33.6-147.fc13.x86_64
package: rapidsvn-0.12.0-1.fc13
rating: 4
reason: Process /usr/bin/rapidsvn was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 Giuliano Catrambone 2010-08-02 10:05:16 UTC 
Created attachment 435991 [details]
File: backtrace
Comment 2 Tim Jackson 2010-09-11 13:48:36 UTC 
Thank you for the report. As advised by the RapidSVN authors, this has been reported in the upstream bugtracker:
http://rapidsvn.tigris.org/issues/show_bug.cgi?id=720
Note You need to log in before you can comment on or make changes to this bug.