On Oct 21, 2008, at 13:26 , Georg S. Weber wrote:
> > Hi, > > On 21 Okt., 20:59, Emmanuel Thomé <[EMAIL PROTECTED]> wrote: >> Hmm, it turns out that it's not just any code that triggers this >> behaviour. However, with the following test case I can reproduce the >> problem quite deterministically: >> >> (term1): strace -p `pidof sage.bin` -e trace='stat' >> >> (term2): >> sage: for i in range(100): float(1)/2 >> > > thanks for reporting this issue! > > It's a very nice mind teaser to ponder about. > > Since I have currently only Mac boxes in my reach, and on Mac OS X, > there does not seem to be neither "strace" nor "pidof", I only can try > to put pure thought on this one. FWIW, Mac OS X does have a variety of tools to help with this kind of thing. See, among others, sc_usage (system calls), fs_usage (file- system-specific calls), latency, Shark, and sample/Sample (the capitalized ones are in the Xcode suite - whereever you installed - in various directories under Applications/). Justin -- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds ----------- I'm beginning to like the cut of his jibberish. ----------- --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
