Staging
v0.5.1
v0.5.1
https://github.com/python/cpython
Revision a40c793d06ee2b42a5013015352616b4ca6b288b authored by Tim Peters on 05 September 2001, 22:36:56 UTC, committed by Tim Peters on 05 September 2001, 22:36:56 UTC
requires that errno ever get set, and it looks like glibc is already playing that game. New rules: + Never use HUGE_VAL. Use the new Py_HUGE_VAL instead. + Never believe errno. If overflow is the only thing you're interested in, use the new Py_OVERFLOWED(x) macro. If you're interested in any libm errors, use the new Py_SET_ERANGE_IF_OVERFLOW(x) macro, which attempts to set errno the way C89 said it worked. Unfortunately, none of these are reliable, but they work on Windows and I *expect* under glibc too.
1 parent 75ed167
Tip revision: a40c793d06ee2b42a5013015352616b4ca6b288b authored by Tim Peters on 05 September 2001, 22:36:56 UTC
Rework the way we try to check for libm overflow, given that C99 no longer
Rework the way we try to check for libm overflow, given that C99 no longer
Tip revision: a40c793
gdbinit
# -*- ksh -*-
#
# If you use the GNU debugger gdb to debug the Python C runtime, you
# might find some of the following commands useful. Copy this to your
# ~/.gdbinit file and it'll get loaded into gdb automatically when you
# start it up. Then, at the gdb prompt you can do things like:
#
# (gdb) pyo apyobjectptr
# <module 'foobar' (built-in)>
# refcounts: 1
# address : 84a7a2c
# $1 = void
# (gdb)
# Prints a representation of the object to stderr, along with the
# number of reference counts it current has and the hex address the
# object is allocated at. The argument must be a PyObject*
define pyo
print _PyObject_Dump($arg0)
end
# Prints a representation of the object to stderr, along with the
# number of reference counts it current has and the hex address the
# object is allocated at. The argument must be a PyGC_Head*
define pyg
print _PyGC_Dump($arg0)
end
Computing file changes ...
