Bug 118179 - [Subversion] Vim: Caught deadly signal SEGV
Summary: [Subversion] Vim: Caught deadly signal SEGV
Status: RESOLVED DUPLICATE of bug 112930
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: ConsoleApps (show other bugs)
Version: RC 4
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Mads Martin Joergensen
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-21 07:38 UTC by Thomas Schraitle
Modified: 2005-09-21 08:10 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Schraitle 2005-09-21 07:38:31 UTC 
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.
Comment 1 Mads Martin Joergensen 2005-09-21 08:10:54 UTC 

*** This bug has been marked as a duplicate of 112930 ***