subversion segfault with snapshot 20121215
marco atzeri
marco.atzeri@gmail.com
Tue Dec 18 17:00:00 GMT 2012
On 12/18/2012 5:42 PM, Christopher Faylor wrote:
> On Tue, Dec 18, 2012 at 05:25:24PM +0100, marco atzeri wrote:
>> On 12/18/2012 3:27 PM, Corinna Vinschen wrote:
>>> On Dec 18 15:12, marco atzeri wrote:
>>>>
>>>> just noted that
>>>>
>>>> $ svn checkout
>>>> http://svn.code.sf.net/p/octave/code/trunk/octave-forge/ octave-code
>>>>
>>>> segfaults with snapshot and works fine with 1.7.17,
>>>> so I guess it is snapshot problem
>>>
>>> Which snapshot introduced the problem?
>>
>> first after 1.7.17
>> 20121123.
>>
>> (and of course I tested starting from last one 20121215 and going back)
>
> I added a workaround for this problem to CVS but I'm puzzled about why
> it is happening. For some reason, new() is no longer returning zeroed
> memory. That's pretty troubling.
>
> A new snapshot is being generated now.
>
> cgf
>
svn works thanks.
I will run my usual crash test (build and run octave) to see if anything
else is gone crazy.
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin
mailing list