Bug 821856
| Summary: | [abrt] rapidsvn-0.12.0-4.fc17: svn_wc_check_wc2: Process /usr/bin/rapidsvn was killed by signal 11 (SIGSEGV) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | david.lewis | ||||||||||
| Component: | rapidsvn | Assignee: | Tim Jackson <rpm> | ||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 17 | CC: | jerry.levan, rhel, rpm | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:0e256f970bd8396c4917985da79a052c23843539 | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2012-07-03 19:18:31 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
david.lewis
2012-05-15 15:19:33 UTC
Created attachment 584689 [details]
File: backtrace
Created attachment 584690 [details]
File: maps
Created attachment 584691 [details]
File: dso_list
Created attachment 584692 [details]
File: build_ids
Checking out a repository backtrace_rating: 4 Package: rapidsvn-0.12.0-4.fc17 OS Release: Fedora release 17 (Beefy Miracle) Possibly a duplicate of bug #827102 I dpn't seem to be able to 'checkout' a project. The target directory gets created but rapidsvn immediately dies with a seg violation before any files get moved from the repository. Check the latest update 0.12.1 over in bug #827102, I think that will fix it *** This bug has been marked as a duplicate of bug 827102 *** |