homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author meador.inge
Recipients benjamin.peterson, meador.inge, petri.lehtinen, skrah
Date 2012年02月16日.04:18:57
SpamBayes Score 0.0007503334
Marked as misclassified No
Message-id <1329365939.45.0.640860413861.issue13089@psf.upfronthosting.co.za>
In-reply-to
Content
Stefan, how did you reproduce this? I tried:
1. Uncommenting '#define Py_USING_MEMORY_DEBUGGER' in 
 'Objects/obmalloc.c'.
2. Configuring with './configure --without-pymalloc'.
3. Running 'valgrind --tool=memcheck --log-file=leaks.txt
 --leak-check=full --suppressions=Misc/valgrind-python.supp
 ./python -m test test_mailbox'.
When performing the above I only see leaks in import:
==2683== 256 bytes in 1 blocks are definitely lost in loss record 3,234 of 4,881
==2683== at 0x4A074CD: malloc (vg_replace_malloc.c:236)
==2683== by 0xD0753A1: PyInit_atexit (atexitmodule.c:294)
==2683== by 0x49AE0B: _PyImport_LoadDynamicModule (importdl.c:85)
==2683== by 0x498740: import_submodule (import.c:3338)
==2683== by 0x4989CA: load_next (import.c:3149)
==2683== by 0x499005: import_module_level.isra.10 (import.c:2842)
==2683== by 0x499759: PyImport_ImportModuleLevelObject (import.c:2904)
==2683== by 0x4729EA: builtin___import__ (bltinmodule.c:195)
==2683== by 0x5064E9: PyObject_Call (abstract.c:2150)
==2683== by 0x473E3E: PyEval_CallObjectWithKeywords.constprop.8 (ceval.c:3931)
==2683== by 0x477D83: PyEval_EvalFrameEx (ceval.c:2332)
==2683== by 0x4752FB: PyEval_EvalCodeEx (ceval.c:3426)
History
Date User Action Args
2012年02月16日 04:18:59meador.ingesetrecipients: + meador.inge, benjamin.peterson, skrah, petri.lehtinen
2012年02月16日 04:18:59meador.ingesetmessageid: <1329365939.45.0.640860413861.issue13089@psf.upfronthosting.co.za>
2012年02月16日 04:18:58meador.ingelinkissue13089 messages
2012年02月16日 04:18:57meador.ingecreate

AltStyle によって変換されたページ (->オリジナル) /