On Jul 26, 2006, at 7:25am, "M. Levinson" writes: >On Jul 24, 2006, at 7:01pm, Witold Filipczyk writes: >>If you know Python could you say why >>$ valgrind elinks >>shows a lot of errors in the Python part of code? > >I'll be happy to take a look if I can get valgrind to run. (From a quick >first glance at http://valgrind.org/ it doesn't appear to support my >non-Linux platform....)
Okay, I was able to exhume an old Linux box and take a look at valgrind. I saw valgrind errors related to Python's internal object allocator. Those appear to be expected; the Python distribution includes a detailed explanation in Misc/README.valgrind, which also documents several ways to suppress spurious errors. I tried two of the suggested approaches (first building Python without the PyMalloc allocator, and then rebuilding Python with Py_USING_MEMORY_DEBUGGER and using the valgrind suppressions file provided in the Python distribution). In both cases "valgrind elinks" produced no further errors related to the Python backend, so in my testing I didn't see evidence of actual problems in the Python part of the code. _______________________________________________ elinks-dev mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-dev
