Hey!

I was taking a look and the issue is not reproducible in trunk, since
r145271 seems to fix it indirectly, by calling MonoIO.Write until *all* the
bytes have been written.

At least it fixes the very specific scenario described in the bug report,
and since that revision is expected to be backported, we should at least do
it.

Carlos.

2010/2/6 Miguel de Icaza <mig...@novell.com>

> > > I've filed a somewhat nasty bug a few days back (you may lose your data
> > > if you trigger it): https://bugzilla.novell.com/show_bug.cgi?id=575813
> > >
> > > I'd really appreciate if someone could take a look at this.
> >
> > BUMP!  Doesn't anyone think it's a critical bug?
>
> The fix is trivial, the side effects are far reaching and any fix will
> require a careful review of those side effects.
>
> I would not expect a resolution any time soon.
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Reply via email to