Re: svn commit: r15154 - in trunk: subversion/bindings/swig/ruby/libsvn_swig_ruby subversion/bindings/swig/ruby/svn subversion/bindings/swig/ruby/test tools/examples tools/hook-scripts

Hi,

In <df2177af05070211583be9ae21@mail.gmail.com>
  "Re: svn commit: r15154 - in trunk: subversion/bindings/swig/ruby/libsvn_swig_ruby subversion/bindings/swig/ruby/svn subversion/bindings/swig/ruby/test tools/examples tools/hook-scripts" on Sat, 2 Jul 2005 14:58:21 -0400,
  David James <james82@gmail.com> wrote:

> Kouhei, are there any safeguards in place here to prevent Ruby from
> destroying a pool when references to its children still exist? I tried
> using this code for the Python bindings and ran into problems. Here
> are some examples.
>
> Example crash #1:
> >>> pool = apr_pool_t()
> >>> pool2 = apr_pool_t(pool)
> >>> del pool
> >>> del pool2
> zsh: segmentation fault python
>
> Example crash #2:
> >>> pool = None
> >>> def someFunction():
> ... pool2 = apr_pool_t()
> ... pool = apr_pool_t(pool2)
> ...
> >>> someFunction()
> zsh: segmentation fault python

Thanks for information.

This problem isn't occurred on Ruby bindings. Because a pool
of Ruby bindings has reference of parent pool, now.

Thanks,

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