On Thu, Jul 11, 2013 at 8:35 PM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Thu, Jul 11, 2013 at 07:47:19PM +0400, Pavel Borzenkov wrote:
>> Hi,
>>
>> after update to svn 1.8.0 I have 100% reproducible perl crash during
>> 'git svn fetch' with the following error (full backtrace + link to
>> core at the end of the message):
>>
>> *** Error in `/usr/bin/perl': double free or corruption (!prev):
>> 0x000000000332fc90 ***
>>
>> Downgrading to 1.7.10 helps.
>> Any advice on what could be the reason?
>
> From the backtrace you provided, it looks like a pool cleanup handler
> is trying to free memory that is already freed, or is trying to free
> an invalid pointer. It's hard to say where the problem originates
> since at the time the pool cleanup handler runs the error has already
> happened elsewhere. Off-hand, I don't know what could be going wrong.
>
> This could well be a bug in Subversion 1.8. Or it could be a bug
> in the perl script (because, yes, perl scripts need to manage
> memory when using the swig bindings -- the bindings are a straight
> wrapper around the C API and do not abstract memory management
> away from the scripting language).
>
> Can you run this script in Valgrind or a similar analysis tool?
Sure. Will do in a couple of days.
> That might help shed more light on the issue.
Received on 2013-07-11 18:55:47 CEST