| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Added checks for integer overflows, contributed by Google. Some are
only available if asserts are left in the code, in cases where they
can't be triggered from Python code.
|
| | |
|
| | |
|
| |
|
|
| |
rather than only looking at the type - this was broken in 2.3.
|
| | |
|
| |
|
|
| |
to an uninitialized pointer: fixes the problem and adds a test case
|
| |
|
|
|
|
|
|
| |
- fixes various memory leaks found by valgrind and a follup closer
code inspection of the bsddb module. (merges r1.32 of _bsddb.c
and an associated test case)
- also merges the one line r1.37 _bsddb.c fix that fixes a leak on
the rare DBEnv creation failed error path.
|
| |
|
|
|
|
|
| |
the end of a second function whos code was identical enough for patch
not to reject the patch. this reverses that misapplication (only the
DBC_set_range method needed modification, not DBC_set as well). This
problem only exists in the release32-maint branch.
|
| |
|
|
|
|
| |
revision 1.17.4.1
date: 2003/11/03 21:37:43; author: greg; state: Exp; lines: +9 -9
* SF patch 835100 - C++ // comments are not allowed. use /* */
|
| | |
|
| |
|
|
|
|
|
| |
Also revise a related function to minimise file handle/pipe leakage
and improve reliability.
Backported from -HEAD.
|
| |
|
|
| |
pass over the unreachable weakrefs-with-callbacks to unreachable objects.
|
| |
|
|
|
|
|
|
| |
In cyclic gc, clear all weakrefs to unreachable objects before allowing any
Python code (weakref callbacks or __del__ methods) to run.
This is a critical bugfix, affecting all versions of Python since weakrefs
were introduced.
|
| | |
|
| |
|
|
| |
their txn argument.
|
| |
|
|
| |
to the 2.3 maint branch.
|
| |
|
|
|
|
|
| |
in Python 2.3.
Taken from HEAD, tested as part of the unstable and testing Debian packages since May on
various architectures.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
compatibility with various broken SSL implementations out there.
|
| |
|
|
| |
#984672 by James Lamanna
|
| |
|
|
| |
Closes bug #978645.
|
| |
|
|
|
| |
datetime.date, datetime.datetime and datetime.time could yield insane
objects. Thanks to Jiwon Seo for a fix.
|
| |
|
|
|
|
|
|
|
| |
Fix for #932977: MacOSX does not pass the whole pathname in argv[0] for
#!-scripts, only the filename part, and this can lead to incorrect
initialization of sys.path and sys.executable if there is another python
on $PATH before the one used in #!.
The fix was picked up from the darwinports crowd, thanks!
|
| | |
|
| |
|
|
| |
Closes #513572.
|
| |
|
|
| |
from trying to do msync(-1);munmap(-1).
|
| |
|
|
|
|
|
| |
binascii_a2b_qp() and binascii_b2a_qp() with calls to PyMem_Malloc() and
PyMem_Free(). These won't return NULL unless the allocations actually fail,
so it won't trigger a bogus memory error on some platforms <cough>AIX</cough>
when passed a length of zero.
|
| |
|
|
| |
avoid breaking the build on MkLinux (Linux 2.0).
|
| |
|
|
|
| |
Both cycle() and chain() were handling exceptions only when switching
input sources. The patch makes the handle more immediate.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Fixes for AF_UNIX support on OS/2:
- return the full size of the sockaddr_un structure, without which
bind() fails with EINVAL;
- set test_socketserver to use a socket name that meets the form
required by the underlying implementation;
- don't bother exercising the forking AF_UNIX tests on EMX - its
fork() can't handle the stress.
|
| |
|
|
|
|
| |
OS/2's TCP/IP stack supports AF_UNIX sockets, with the limitation that
the socket name must start with /socket32/. Unlike Unix systems, this
file never exists in the file system.
|
| |
|
|
|
|
|
|
| |
OS/2 has support for spawnvp() and spawnvpe() in the C libraries supplied
with major C compilers (VACPP, EMX+gcc and [Open]Watcom).
Also tidy up the export of spawn*() symbols in the os module to match what
is found/implemented.
|
| | |
|
| |
|
|
| |
bad file descriptor. Fixes SF Bug #850981
|
| |
|
|
| |
[Bug #920575] Add a workaround for GNU libc nl_langinfo()'s returning NULL.
|
| |
|
|
| |
free() on something it did not allocate for non B-Tree based databases.
|
| |
|
|
|
|
|
|
|
| |
* Fixed a bug in the compatibility interface set_location() method
where it would not properly search to the next nearest key when
used on BTree databases. [SF bug id 788421]
* Fixed a bug in the compatibility interface set_location() method
where it could crash when looking up keys in a hash or recno
format database due to an incorrect free().
|
| | |
|
| |
|
|
| |
messages.
|
| |
|
|
| |
messages.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Indented because it was incomprehensible. "Repaired" means someone
checked in a change that screwed up the multiple nesting levels, causing
USE_RECURSION_LIMIT to stop getting defined on all non-LP64 boxes other
than FreeBSD. Tried to repair that in a more-robust way. That error
in turn caused a bogus change to get checked in to test_re.py, which I
repaired earlier.
This needs fresh testing on all non-Win32 platforms (Win32 never used
USE_RECURSION_LIMIT, and still doesn't). Running the standard test_re.py
is an adequate test.
|