On Sat, 2012-03-03 at 23:57 +0100, Jelmer Vernooij wrote:
> 
> Thanks for the bug report, and sorry for not getting back to you
> earlier. I've tried to reproduce this locally for the last couple of
> days, but have failed. I'm using a slightly newer version of bzr-git,
> but there have been no changes to the SQL side of things in a long
> time. 
> 
> Cloning debbugs works fine here. Unity still fails, but later in the
> process and with different errors than you're getting.
> 
> I wonder if the glibc realloc error is related - I'm not seeing that.

You seem to be correct. Looks like my issue is that I set MALLOC_CHECK_
and MALLOC_PERTURB_ in my shell environment. If I unset them then I get
different failures with the versions from testing. It appears that some
part of the stack is causing heap consistency issues:

http://www.gnu.org/s/libc/manual/html_node/Heap-Consistency-Checking.html
http://udrepper.livejournal.com/11429.html
https://lists.fedoraproject.org/pipermail/devel/2010-May/135667.html

> If you have a sid install around, it would be great if you could try
> git-remote-bzr on that with the current Python package there.

I have unstable in my sources.list, but held back with pinning. After
upgrading python2.7, bzr, python-bzrlib, bzr-git, bzr-gtk I get no
failure cloning bzr-stats with MALLOC_CHECK_ and MALLOC_PERTURB_ unset,
lp:unity fails with a different error and debbugs is taking ages.

That said, the resulting git repositories have some issues with gitk and
the bash shell prompt git functions, bzr-stats for example: git tag
complains about duplicate tags and gitk also complains about an error
parsing revisions.

With upgraded python2.7, bzr, python-bzrlib, bzr-git, bzr-gtk and both
MALLOC_CHECK_ and MALLOC_PERTURB_ *set*, `git clone bzr::lp:bzr-stats`
fails silently and dumps a core file (I have that turned on),
unfortunately the stack trace that results is quite useless.

How do you want to proceed here?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to