➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2004-01-21 09:35 by schiotz, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| fido | schiotz, 2004-01-21 09:35 | Output from profiler / pstat | ||
| Messages (2) | |||
|---|---|---|---|
| msg19736 - (view) | Author: Jakob Schiøtz (schiotz) | Date: 2004-01-21 09:35 | |
When profiling code that runs very long (36 hours), negative times are reported. I suspect an integer overflow somewhere. |
|||
| msg79675 - (view) | Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) *  |
Date: 2009-01-12 13:31 | |
on POSIX, clock() indeed wraps around after some time. This was corrected with issue645894, and is available since python 2.5. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:02 | admin | set | github: 39843 |
| 2009-01-12 13:31:00 | amaury.forgeotdarc | set | status: open -> closed resolution: out of date superseder: better timer resolution for profile.py messages: + msg79675 nosy: + amaury.forgeotdarc |
| 2004-01-21 09:35:31 | schiotz | create | |