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

Re: 1.3RC status

From: Kouhei Sutou <kou_at_cozmixng.org>
Date: 2005-10-19 02:58:24 CEST


In <7edfeeef0510181427j3fce69erad999d7ab80f054e@mail.gmail.com>
  "Re: 1.3RC status" on Tue, 18 Oct 2005 14:27:49 -0700,
  Garrett Rooney <rooneg@electricjellyfish.net> wrote:

> > * 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.

I couldn't reproduce the problem on Linux/i386, Linux/amd64,
FreeBSD/i386 and FreeBSD/amd64.

Can I merge r16744 to get more information from
svn-breakage@ list?

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

A debug version Ruby doesn't help you. It's a problem in
Ruby bindings, not Ruby. Could you show me the result of
'make check-swig-rb'? If you run ./configure with
--with-ruby-test-verbose=verbose option, the result will
have more information.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 19 02:59:35 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.