[cvsnt] Re: Problem wit binary files after upgrading server from 2.5.01.1976 to 2.5.03.2151

Michael Wojcik Michael.Wojcik at microfocus.com
Thu Feb 9 15:10:32 GMT 2006


Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


> From: cvsnt-bounces at cvsnt.org 
> [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Daniel Lapolla
> Sent: Thursday, 09 February, 2006 08:43
> 
> Tony Hoyle wrote:
> > Daniel Lapolla wrote:
> >>
> >> cvs commit -f -m "no message" -- Document01.doc (in 
> directory E:\test)
> >> Checking in Document01.doc;
> >> /test_repository/test_module/Document01.doc,v  <--  Document01.doc
> >> cvs commit: warning: unrecognized response `free(): 
> invalid pointer 
> >> 0x9f482f0!' from cvs server
> >>
> > Nope.. it's not an error from cvs itself - something from the
libraries 
> > I think.  you'd need to look at the documentation to see if you get
make 
> > it break into gdb or write a backtrace or something.
> 
> Could you provide (or point where we can find) the library versions 
> (used by CVSNT) of your reference configuration so we can compare it 
> with our system?
> 
> Our idea is to build CVSNT against the recommended versions and to
point 
> it to the correct libs in the production envirnment.

That will trade fail-to-safe behavior for undefined behavior.  Bad idea.
Your files could be silently corrupted.

This is a bug in CVSNT or something that it calls, and it needs to be
found and fixed.

-- 
Michael Wojcik
Principal Software Systems Developer, Micro Focus



More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook