Bugs item #1721309, was opened at 2007-05-18 15:42
Message generated for change (Comment added) made by loewis
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1721309&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: David Favor (dfavor)
Assigned to: Nobody/Anonymous (nobody)
Summary: make testall shows many glibc detected malloc corruptions
Initial Comment:
export _MALLOC_CHECK_=1
make testall
test_bsddb3
*** glibc detected *** ./python: free(): invalid pointer: 0x40b92de4 ***
*** glibc detected *** ./python: free(): invalid pointer: 0x40b92de4 ***
*** glibc detected *** ./python: free(): invalid pointer: 0x40b92de4 ***
*** glibc detected *** ./python: free(): invalid pointer: 0x40b92de4 ***
*** glibc detected *** ./python: free(): invalid pointer: 0x40b92de4 ***
*** glibc detected *** ./python: free(): invalid pointer: 0x40b92de4 ***
followed by deadlock errors.
malloc: using debugging hooks
blattest test_tempfile failed -- Traceback (most recent call last):
File "/build/work/Python-2.5.1/Lib/test/test_tempfile.py", line 310, in
test_noinherit
self.failIf(retval > 0, "child process reports failure %d"%retval)
AssertionError: child process reports failure 1
test_timeout
test test_timeout failed -- Traceback (most recent call last):
File "/build/work/Python-2.5.1/Lib/test/test_timeout.py", line 128, in
testConnectTimeout
%(_delta, self.fuzz, _timeout))
AssertionError: timeout (8.20631) is more than 2 seconds more than expected
(0.001)
----------------------------------------------------------------------
>Comment By: Martin v. Löwis (loewis)
Date: 2007-05-18 19:43
Message:
Logged In: YES
user_id=21627
Originator: NO
Unfortunately, I cannot reproduce this problem on Debian unstable (x86,
gcc 4.1.3, glibc 2.5) -
the test passes just fine with _MALLOC_CHECK set.
Can you provide a few more details: glibc version, compiler version, Linux
distribution, processor architecture, precise Python version being test,
does the error happen on the first or a subsequent cycle of all tests?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1721309&group_id=5470
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
