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
Miguel de Icaza wrote:
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
On Mon, 2010-02-08 at 15:07 +0200, Alex Shulgin wrote:
Miguel de Icaza wrote:
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!
Sebastien Pouliot wrote:
On Mon, 2010-02-08 at 15:07 +0200, Alex Shulgin wrote:
BTW, couldn't this type of programming errors be caught by lint-like
tools for static code analysis?
Yes. Finding *potential* errors is easy. Automatically spotting errors
that matters, like the above case,
On Mon, 2010-02-08 at 17:07 +0200, Alex Shulgin wrote:
Sebastien Pouliot wrote:
On Mon, 2010-02-08 at 15:07 +0200, Alex Shulgin wrote:
BTW, couldn't this type of programming errors be caught by lint-like
tools for static code analysis?
Yes. Finding *potential* errors is easy.
Sebastien Pouliot wrote:
On Mon, 2010-02-08 at 17:07 +0200, Alex Shulgin wrote:
Sebastien Pouliot wrote:
On Mon, 2010-02-08 at 15:07 +0200, Alex Shulgin wrote:
BTW, couldn't this type of programming errors be caught by lint-like
tools for static code analysis?
Yes. Finding *potential*
Leszek Ciesielski wrote:
On Mon, Feb 8, 2010 at 4:34 PM, Alex Shulgin
alexander.shul...@yessoftware.com wrote:
Is there someone at Novell being paid to support Mono corlib? I guess
there is or should be one...
Yes, there are people paid to develop corlib and other Mono parts. If
you do
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
Alex Shulgin wrote:
Hi,
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?
--
Alex
I will take a look at it in the next days.
Carlos.
2010/2/5 Alex Shulgin alexander.shul...@yessoftware.com
Alex Shulgin wrote:
Hi,
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
Carlos Alberto Cortez wrote:
I will take a look at it in the next days.
OK, thanks for that! :)
--
Alex
2010/2/5 Alex Shulgin alexander.shul...@yessoftware.com
mailto:alexander.shul...@yessoftware.com
Alex Shulgin wrote:
Hi,
I've filed a somewhat nasty bug a few
Hi,
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.
--
Cheers,
Alex
___
Mono-devel-list mailing
12 matches
Mail list logo
