Bug 739297 - [abrt] rapidsvn-0.12.0-2.fc14: Process /usr/bin/rapidsvn was killed by signal 6 (SIGABRT)
Summary: [abrt] rapidsvn-0.12.0-2.fc14: Process /usr/bin/rapidsvn was killed by signal...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rapidsvn
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5f0b677a04d41472976277b9625...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-17 11:08 UTC by Raffael Luthiger
Modified: 2011-10-09 20:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-09 20:27:37 UTC


Attachments (Terms of Use)
File: backtrace (33.74 KB, text/plain)
2011-09-17 11:09 UTC, Raffael Luthiger
no flags Details

Description Raffael Luthiger 2011-09-17 11:08:59 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 34545 bytes
cmdline: rapidsvn
component: rapidsvn
Attached file: coredump, 64892928 bytes
crash_function: __cxxabiv1::__cxa_pure_virtual
executable: /usr/bin/rapidsvn
kernel: 2.6.35.14-96.fc14.x86_64
package: rapidsvn-0.12.0-2.fc14
rating: 4
reason: Process /usr/bin/rapidsvn was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1316257449
uid: 500

How to reproduce
-----
1. I started a commit.
2. I closed the program before the commit finished.
3.

Comment 1 Raffael Luthiger 2011-09-17 11:09:02 UTC
Created attachment 523701 [details]
File: backtrace

Comment 2 Tim Jackson 2011-10-09 20:27:37 UTC
Thank you for the crash report.

Unfortunately, the developers of RapidSVN have reported that they do not have the resources to process Fedora ABRT reports at the present time. If you are able to reproduce this problem, and are willing to work together directly with the developers on this issue, you should contact the rapidsvn-devel mailing list:

http://rapidsvn.tigris.org/ds/viewForumSummary.do?dsForumId=668


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