Bug 63365
Summary: | "cvs rdiff -D" segmentation fault | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Mark Harig <maharig> |
Component: | cvs | Assignee: | Martin Stransky <stransky> |
Status: | CLOSED RAWHIDE | QA Contact: | Ben Levenson <benl> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-03-17 10:39:47 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: |
Description
Mark Harig
2002-04-12 23:20:09 UTC
Here is some additional information about what is causing CVS to generate the segmentation fault. I found the following ill-formed repository file, "Makefile,v" in one of the directories in my CVS repository: > head ; > access ; > symbols ; > locks ; strict; > comment @# @; > > > desc > @@ > > > After I removed this file, the "cvs rdiff" command completed successfully. Of course, generating a segmentation fault is not a good method to report this invalid file format. The short-term workaround for this bug is to: 1) search your CVS repository for the core file, finding the directory in which it was written. 2) check the format of the files in that directory using "cvs update". update responds with the message: cvs update: nothing known about <your broken file> 3) remove the corresponding ",v" file from the repository. 4) repeat until all invalid ",v" files have been removed from the repository. The "cvs rdiff" command should then run to completion without any errors. |