mirror of
https://github.com/python/cpython.git
synced 2025-07-13 22:35:18 +00:00
ddea208be9
When WITH_PYMALLOC is defined, define PYMALLOC_DEBUG to enable the debug allocator. This can be done independent of build type (release or debug). A debug build automatically defines PYMALLOC_DEBUG when pymalloc is enabled. It's a detected error to define PYMALLOC_DEBUG when pymalloc isn't enabled. Two debugging entry points defined only under PYMALLOC_DEBUG: + _PyMalloc_DebugCheckAddress(const void *p) can be used (e.g., from gdb) to sanity-check a memory block obtained from pymalloc. It sprays info to stderr (see next) and dies via Py_FatalError if the block is detectably damaged. + _PyMalloc_DebugDumpAddress(const void *p) can be used to spray info about a debug memory block to stderr. A tiny start at implementing "API family" checks isn't good for anything yet. _PyMalloc_DebugRealloc() has been optimized to do little when the new size is <= old size. However, if the new size is larger, it really can't call the underlying realloc() routine without either violating its contract, or knowing something non-trivial about how the underlying realloc() works. A memcpy is always done in this case. This was a disaster for (and only) one of the std tests: test_bufio creates single text file lines up to a million characters long. On Windows, fileobject.c's get_line() uses the horridly funky getline_via_fgets(), which keeps growing and growing a string object hoping to find a newline. It grew the string object 1000 bytes each time, so for a million-character string it took approximately forever (I gave up after a few minutes). So, also: fileobject.c, getline_via_fgets(): When a single line is outrageously long, grow the string object at a mildly exponential rate, instead of just 1000 bytes at a time. That's enough so that a debug-build test_bufio finishes in about 5 seconds on my Win98SE box. I'm curious to try this on Win2K, because it has very different memory behavior than Win9X, and test_bufio always took a factor of 10 longer to complete on Win2K. It *could* be that the endless reallocs were simply killing it on Win2K even in the release build.
143 lines
3.3 KiB
C
143 lines
3.3 KiB
C
#ifndef Py_PYTHON_H
|
|
#define Py_PYTHON_H
|
|
/* Since this is a "meta-include" file, no #ifdef __cplusplus / extern "C" { */
|
|
|
|
|
|
/* Enable compiler features; switching on C lib defines doesn't work
|
|
here, because the symbols haven't necessarily been defined yet. */
|
|
#ifndef _GNU_SOURCE
|
|
# define _GNU_SOURCE 1
|
|
#endif
|
|
|
|
/* Forcing SUSv2 compatibility still produces problems on some
|
|
platforms, True64 and SGI IRIX begin two of them, so for now the
|
|
define is switched off. */
|
|
#if 0
|
|
#ifndef _XOPEN_SOURCE
|
|
# define _XOPEN_SOURCE 500
|
|
#endif
|
|
#endif
|
|
|
|
/* Include nearly all Python header files */
|
|
|
|
#include "patchlevel.h"
|
|
#include "pyconfig.h"
|
|
|
|
#ifdef HAVE_LIMITS_H
|
|
#include <limits.h>
|
|
#endif
|
|
|
|
/* pyconfig.h may or may not define DL_IMPORT */
|
|
#ifndef DL_IMPORT /* declarations for DLL import/export */
|
|
#define DL_IMPORT(RTYPE) RTYPE
|
|
#endif
|
|
#ifndef DL_EXPORT /* declarations for DLL import/export */
|
|
#define DL_EXPORT(RTYPE) RTYPE
|
|
#endif
|
|
|
|
#if defined(__sgi) && defined(WITH_THREAD) && !defined(_SGI_MP_SOURCE)
|
|
#define _SGI_MP_SOURCE
|
|
#endif
|
|
|
|
#include <stdio.h>
|
|
#ifndef NULL
|
|
# error "Python.h requires that stdio.h define NULL."
|
|
#endif
|
|
|
|
#include <string.h>
|
|
#include <errno.h>
|
|
#ifdef HAVE_STDLIB_H
|
|
#include <stdlib.h>
|
|
#endif
|
|
#ifdef HAVE_UNISTD_H
|
|
#include <unistd.h>
|
|
#endif
|
|
|
|
/* CAUTION: Build setups should ensure that NDEBUG is defined on the
|
|
* compiler command line when building Python in release mode; else
|
|
* assert() calls won't be removed.
|
|
*/
|
|
#include <assert.h>
|
|
|
|
#include "pyport.h"
|
|
|
|
/* Debug-mode build with pymalloc implies PYMALLOC_DEBUG.
|
|
* PYMALLOC_DEBUG is in error if pymalloc is not in use.
|
|
*/
|
|
#if defined(Py_DEBUG) && defined(WITH_PYMALLOC) && !defined(PYMALLOC_DEBUG)
|
|
#define PYMALLOC_DEBUG
|
|
#endif
|
|
#if defined(PYMALLOC_DEBUG) && !defined(WITH_PYMALLOC)
|
|
#error "PYMALLOC_DEBUG requires WITH_PYMALLOC"
|
|
#endif
|
|
#include "pymem.h"
|
|
|
|
#include "object.h"
|
|
#include "objimpl.h"
|
|
|
|
#include "pydebug.h"
|
|
|
|
#include "unicodeobject.h"
|
|
#include "intobject.h"
|
|
#include "longobject.h"
|
|
#include "floatobject.h"
|
|
#ifndef WITHOUT_COMPLEX
|
|
#include "complexobject.h"
|
|
#endif
|
|
#include "rangeobject.h"
|
|
#include "stringobject.h"
|
|
#include "bufferobject.h"
|
|
#include "tupleobject.h"
|
|
#include "listobject.h"
|
|
#include "dictobject.h"
|
|
#include "methodobject.h"
|
|
#include "moduleobject.h"
|
|
#include "funcobject.h"
|
|
#include "classobject.h"
|
|
#include "fileobject.h"
|
|
#include "cobject.h"
|
|
#include "traceback.h"
|
|
#include "sliceobject.h"
|
|
#include "cellobject.h"
|
|
#include "iterobject.h"
|
|
#include "descrobject.h"
|
|
#include "weakrefobject.h"
|
|
|
|
#include "codecs.h"
|
|
#include "pyerrors.h"
|
|
|
|
#include "pystate.h"
|
|
|
|
#include "modsupport.h"
|
|
#include "pythonrun.h"
|
|
#include "ceval.h"
|
|
#include "sysmodule.h"
|
|
#include "intrcheck.h"
|
|
#include "import.h"
|
|
|
|
#include "abstract.h"
|
|
|
|
#define PyArg_GetInt(v, a) PyArg_Parse((v), "i", (a))
|
|
#define PyArg_NoArgs(v) PyArg_Parse(v, "")
|
|
|
|
/* Convert a possibly signed character to a nonnegative int */
|
|
/* XXX This assumes characters are 8 bits wide */
|
|
#ifdef __CHAR_UNSIGNED__
|
|
#define Py_CHARMASK(c) (c)
|
|
#else
|
|
#define Py_CHARMASK(c) ((c) & 0xff)
|
|
#endif
|
|
|
|
#include "pyfpe.h"
|
|
|
|
/* These definitions must match corresponding definitions in graminit.h.
|
|
There's code in compile.c that checks that they are the same. */
|
|
#define Py_single_input 256
|
|
#define Py_file_input 257
|
|
#define Py_eval_input 258
|
|
|
|
#ifdef HAVE_PTH
|
|
/* GNU pth user-space thread support */
|
|
#include <pth.h>
|
|
#endif
|
|
#endif /* !Py_PYTHON_H */
|