diff options
author | Fred Drake <fdrake@acm.org> | 2000-06-30 15:01:00 (GMT) |
---|---|---|
committer | Fred Drake <fdrake@acm.org> | 2000-06-30 15:01:00 (GMT) |
commit | a44d353e2b6d947d36ab9d36c1fc84335a0878fe (patch) | |
tree | 3d0add21fcb365aeeb5ac6b45add0a30e6f3b93b /Objects/intobject.c | |
parent | d49e5b466731d0e68ea41655aecbe3a66b1976d9 (diff) | |
download | cpython-a44d353e2b6d947d36ab9d36c1fc84335a0878fe.zip cpython-a44d353e2b6d947d36ab9d36c1fc84335a0878fe.tar.gz cpython-a44d353e2b6d947d36ab9d36c1fc84335a0878fe.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 'Objects/intobject.c')
-rw-r--r-- | Objects/intobject.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Objects/intobject.c b/Objects/intobject.c index 2e8939e..d182b30 100644 --- a/Objects/intobject.c +++ b/Objects/intobject.c @@ -957,8 +957,8 @@ PyInt_Fini() i++, p++) { if (PyInt_Check(p) && p->ob_refcnt != 0) fprintf(stderr, - "# <int at %lx, refcnt=%d, val=%ld>\n", - (long)p, p->ob_refcnt, p->ob_ival); + "# <int at %p, refcnt=%d, val=%ld>\n", + p, p->ob_refcnt, p->ob_ival); } list = list->next; } |