trying to make tracebacks reproducible

[Augie Fackler]

On Jul 6, 2010, at 12:49 PM, Christian Ebert wrote:

> * Matt Mackall on Tuesday, July 06, 2010 at 10:49:39 -0500
>> On Tue, 2010-07-06 at 10:16 +0200, Christian Ebert wrote:
>>> * Matt Mackall on Monday, July 05, 2010 at 14:05:49 -0500
>>>> You've probably found a kernel bug. In particular, some failure to
>>>> save/restore floating point state correctly during task switch. Since
>>>> this is expensive, most operating systems try to avoid doing it if
>>>> floating point is not in use by a given task.
>>> 
>>> I see (sort of). Nothing one can do about it then?
>> 
>> Depends on what kernel you're running. If it's Linux, we can fix it
>> (though I'm pretty sure this entire class of bugs was fixed most of a
>> decade ago, which is why I already have a good idea what the problem
>> is).
> 
> Should have mentioned it before:
> 
> $ sw_vers
> ProductName:	Mac OS X
> ProductVersion:	10.5.8
> BuildVersion:	9L30

Have you filed a radar yet? If not, you need to. Even better, post it on openradar, and then follow up to this thread with the link so others can check on its status.

Heck, if you file it in radar with steps to reproduce, and copy it to openradar, I'll try it on my Snow Leopard machine to verify that it's still busted there too (assuming it is) and then duplicate your bug (which is the voting mechanism used by Apple for their internal bugs.)

> 
> Well, too bad. No pager with hg while converting videos, I can
> live with it. Sometimes the clean solution - Broadie's patch - is
> more dirty in the eye of the beholder/user ;-)
> 
> I can still resort to what I used before I switched on the pager
> extension:
> 
> hg diff $@ | colordiff | less -F
> 
> No tracebacks with that.
> 
> Thanks.
> 
> c
> -- 
> The faster we go, the rounder we get.
> --The Grateful Dead
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel