[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Ruby bindings core dump

From: Blair Zajac <blair_at_orcaware.com>
Date: 2007-02-17 22:18:02 CET

Kouhei Sutou wrote:
> Hi,
> In <45D606E4.8050104@orcaware.com>
> "Ruby bindings core dump" on Fri, 16 Feb 2007 11:32:52 -0800,
> Blair Zajac <blair@orcaware.com> wrote:
>> I've been getting consistent core dumps in a simple Ruby script using
>> Ruby 1.8.5-pl2 and Subversion 1.4.3 on a Centos 4.1 box. It creates a
>> Berkeley DB svn repository and then using a wc, just creates top level
>> directories in it and commits into it. At some point, it'll core:
> The reason why it makes core is that
> fs-loader.c:default_warning_func() calls abort(). The reason
> why fs-loader.c:default_warning() is called is that the Ruby
> bindings 1.4.x doesn't clever for memory management. The
> ruby bindings trunk improved that.

Thanks Kou,

Can we merge some of these changes into the 1.4.x branch, or are there
too many changes?

> The following change is a workaround for this problem.
>> (0..1000).each do |i|
>> d = "abc#{i}"
>> puts d
>> make_dir(d)
> GC.start
>> end
> We may think about svn_fs's warning_func API on the Ruby
> bindings. Supporting this feature may cause a problem
> because warning_func may be called after Ruby is cleanuped
> (this case).

Can we have Ruby clean up apr and svn when it cleans itself up?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 17 22:20:33 2007

This is an archived mail posted to the Subversion Dev mailing list.