Re: Ruby bindings core dump

Hi,

In <45D7710A.50904@orcaware.com>
  "Re: Ruby bindings core dump" on Sat, 17 Feb 2007 13:18:02 -0800,
  Blair Zajac <blair@orcaware.com> wrote:

> > 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.
>
> Can we merge some of these changes into the 1.4.x branch, or are there
> too many changes?

The changes are r23251 and r23256. But I've not tried that
the changes can be merged into 1.4.x branch yet... Sorry.

> > 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?

Now, the Ruby bindings' clean up process is the following:

  a Ruby script exits -> run Ruby's GC -> pools are GC'ed
  (warning_func may be called and warning_func may call
  callback written by Ruby. This is a problem because Ruby
  is already in cleanup process) -> atexit(3) ->
  apr_terminate() (warning_func may be called too)

Thanks,

--
kou
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org