On Wed, Jan 14, 2009 at 08:47:34PM -0800, Daniel Burrows <dburr...@debian.org> was heard to say: > Something that would be even better if you can manage it would be to > use "hg bisect". This will be time-consuming, but has the potential to > track down exactly what's happening, or at least what change triggered > it. The one time I was able to (very briefly) reproduce this I tried > running valgrind and gdb, but without getting anywhere.
Bah. There have been too many toolchain changes over the last three years. You can do this, but it'll be a real pain. At the very least you need to use g++ 4.2 and pass --disable-werror. Then, there's the fact that the very first revision that "bisect" picks requires a version of cwidget that no longer exists in Debian... Probably no point in trying to post this to my blog -- hardly anyone would be able to follow the instructions that I'd have to give. Anyway, obviously I would be happy if you could hunt this down, but it's beyond the scope of what I usually ask bug reporters to try, so I'll understand if you don't pursue this approach. Daniel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
