Re: cvs rdiff -t consistently crashes with SEGV when processing files

[Derek Robert Price]

Mark D. Baushke wrote:

> Derek Robert Price <derek@ximbiot.com> writes:
>  
>
> > Mark D. Baushke wrote:
> >    
> >
> > Did you save the command that reproduces the problem to a script?  
> >    
>
> The command was just the 'cvs rdiff -t m' on the repository generated by
> the commands in the script that James provided.
>
>  
>
> > Was it on a temporary repository? 
> >    
>
> Yup, but I still have it around in /tmp/cvs-rdiff-bug
>
>  
>
> > If so, would you mind checking it into sanity.sh on both branches as a
> > one liner tacked onto an rdiff test or something? I tried to check in
> > a test fo this myself, but I could duplicate this with my existing
> > repository and not the repo created by the rdiff test.
> >    
>
> Hmmm... I'll see what I can do.
>
>         -- Mark
>  

Okay, I'm back now and I didn't realize that James provided a script 
initially.  I just saw the command in one of the replies to his email 
and it seg faulted on my repository and I assumed it was all I needed. 
Unless you're almost done with this, I'll do it.

Also, anyone know why CVS isn't leaving core files around anymore?  We 
don't seem to be catching SIGSEGV.  Does catching one of the other 
signals avoid the core?  SIGABRT perhaps?  I seem to remember reading 
something about stopping a core dump via signals before but I can't find 
it now.  I remember a function to throw a core too but I can't find the 
man page for that either.

Derek

--
               *8^)

Email: derek@ximbiot.com

Get CVS support at <http://ximbiot.com>!
--
It is error alone which needs the support of government.  Truth can stand by
itself.
                        - Thomas Jefferson