[issue6061] time.clock(): overflow in programs that run for very long

2009-05-18 Thread Thomas Reiter 

New submission from Thomas Reiter :

On a 64-bit Linux machine the attached program generates the following
(shortened) output:

$ python bug.py
...
after 2145.49s: 
after 2145.82s: 
after 2146.14s: 
after 2146.47s: 
after 2146.80s: 
after 2147.13s: 
after 2147.45s: 
after -2147.19s: 
Here's your bug

-
$ uname -a
Linux  2.6.18-92.1.22.el5 #1 SMP Tue Dec 16 06:45:03 EST 2008 x86_64
x86_64 x86_64 GNU/Linux

$ python -V
Python 2.6

--
components: Library (Lib)
files: bug.py
messages: 88069
nosy: tom65536
severity: normal
status: open
title: time.clock(): overflow in programs that run for very long
type: behavior
versions: Python 2.6
Added file: http://bugs.python.org/file14015/bug.py

___
Python tracker 
<http://bugs.python.org/issue6061>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6061] time.clock(): overflow in programs that run for very long

2009-05-19 Thread Thomas Reiter 

Thomas Reiter  added the comment:

That version of Python is linked against 32-bit libc. Point of overflow
corresponds to
2^31 us.

--
status: open -> closed

___
Python tracker 
<http://bugs.python.org/issue6061>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com