|
Bugzilla – Full Text Bug Listing |
| Summary: | [Subversion] Vim: Caught deadly signal SEGV | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Thomas Schraitle <thomas.schraitle> |
| Component: | ConsoleApps | Assignee: | Mads Martin Joergensen <mmj> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | RC 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Checking in a file with Subversion, I observed a strange behavior: After running "svn co FILENAME" Subversion needs a login message. If I start to type, I get _sometimes_ the following message: -------------------- Vim: Caught deadly signal SEGV *** glibc detected *** free(): invalid pointer: 0x0823bec0 *** Vim: Double signal, exiting svn: Commit failed (details follow): svn: system('vim -c 'set tw=72 et' svn-commit.2.tmp') returned 11 -------------------- The strange thing is, that is not easy to reproduce. However I observed it on two machines, so it might be an undiscovered problem.