diff options
author | Fred Drake <fdrake@acm.org> | 2000-06-30 16:20:13 (GMT) |
---|---|---|
committer | Fred Drake <fdrake@acm.org> | 2000-06-30 16:20:13 (GMT) |
commit | 615ae55eca17c1632e23f52c5842bb338d633ddf (patch) | |
tree | 168f5f6c5b44b133b0d49dbca244776a47db2f9d /Python/thread_lwp.h | |
parent | 4c82b2366ff2eb38f062fc5da1b15ddd1c01fa4b (diff) | |
download | cpython-615ae55eca17c1632e23f52c5842bb338d633ddf.zip cpython-615ae55eca17c1632e23f52c5842bb338d633ddf.tar.gz cpython-615ae55eca17c1632e23f52c5842bb338d633ddf.tar.bz2 |
Trent Mick <trentm@activestate.com>:
The common technique for printing out a pointer has been to cast to a long
and use the "%lx" printf modifier. This is incorrect on Win64 where casting
to a long truncates the pointer. The "%p" formatter should be used instead.
The problem as stated by Tim:
> Unfortunately, the C committee refused to define what %p conversion "looks
> like" -- they explicitly allowed it to be implementation-defined. Older
> versions of Microsoft C even stuck a colon in the middle of the address (in
> the days of segment+offset addressing)!
The result is that the hex value of a pointer will maybe/maybe not have a 0x
prepended to it.
Notes on the patch:
There are two main classes of changes:
- in the various repr() functions that print out pointers
- debugging printf's in the various thread_*.h files (these are why the
patch is large)
Closes SourceForge patch #100505.
Diffstat (limited to 'Python/thread_lwp.h')
0 files changed, 0 insertions, 0 deletions