On 10/18/05, David Anderson <david.anderson@calixo.net> wrote:
> So, things are moving around somewhat. This is the current status of the
> 1.3 branch as far as I know. Please read through and confirm that I'm
> not missing anything - Oh, and that nobody's forgotten about any of this
> stuff :-)
>
> * Ruby bindings segfault. Has this been put to bed? I see the
> STATUS has a couple of approved changes that I'll merge once I'm
> done with this mail. Is there any work or polishing that still
> needs doing, or are we all set? Ah, David James tells me that fix is
> satisfactory as far as 1.3.0 is concerned.
The fix seems fine on /trunk, but merging the last part of it into the
1.3.x branch (r16744, already approved to be merged, just hasn't
actually been merged in) results in segfaults when I run 'make
check-swig-rb'. There don't actually seem to be any substantial
differences between the swig bindings in the branch and the ones in
the trunk (other than this particular revision), so I'm kind of
confused as to what's causing the crash.
Can anybody else reproduce this problem, and if so, any ideas what
causes it? Unfortunately, gdb has yet to tell me anything especially
useful about the crash, I'm going to try building a debug version of
Ruby, to see if that helps...
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 18 23:28:50 2005