Overflow in Python Profiler

[schiotz]

BPO	881261
Nosy	@amauryfa
Superseder	bpo-645894: better timer resolution for profile.py
Files	fido: Output from profiler / pstat

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2009-01-12.13:31:00.977>
created_at = <Date 2004-01-21.09:35:31.000>
labels = ['library']
title = 'Overflow in Python Profiler'
updated_at = <Date 2009-01-12.13:31:00.938>
user = 'https://bugs.python.org/schiotz'

bugs.python.org fields:

activity = <Date 2009-01-12.13:31:00.938>
actor = 'amaury.forgeotdarc'
assignee = 'none'
closed = True
closed_date = <Date 2009-01-12.13:31:00.977>
closer = 'amaury.forgeotdarc'
components = ['Library (Lib)']
creation = <Date 2004-01-21.09:35:31.000>
creator = 'schiotz'
dependencies = []
files = ['1175']
hgrepos = []
issue_num = 881261
keywords = []
message_count = 2.0
messages = ['19736', '79675']
nosy_count = 2.0
nosy_names = ['amaury.forgeotdarc', 'schiotz']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = None
status = 'closed'
superseder = '645894'
type = None
url = 'https://bugs.python.org/issue881261'
versions = ['Python 2.3']

[schiotz]

When profiling code that runs very long (36 hours),
negative times are reported. I suspect an integer
overflow somewhere.

[amauryfa]

on POSIX, clock() indeed wraps around after some time.
This was corrected with bpo-645894, and is available since python 2.5.