Hi Paolo, Thank you for your work investigating this.
On Fri, Nov 17, 2006 at 08:22:34PM +0100, Paolo Molaro wrote: > If I am given access to elara I can try to reproduce that, but it didn't > happen in jitted code and it didn't happen in the 6 builds I ran today > on other boxes: if it's a bug in the runtime it would be common to all > the architectures and unless it has been fixed in mono 1.2.1 already, it > doesn't look common or reproducible. > The patch is here if anyone is interested: > http://lists.ximian.com/pipermail/mono-patches/2006-November/082367.html > but I suggest to go ahead with mono 1.2.1 which should be released on > Monday (we're preparing rc tarballs today). Which based on previous experiences with mono upgrades, means a complete library transition for mono, doesn't it? That would not be acceptable. Even if there's not a library transition, a targetted backport fix would be greatly preferred from a release standpoint. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
