Valgrind + Python: __strcpy_chk warning in PyImport_ImportModuleEx

[Steve G]

>==16039==    at 0x37E2EDBBED: __strcpy_chk (in /lib64/libc-2.3.90.so)
>==16039==    by 0x3B9D79F3CB: (within /usr/lib64/libpython2.4.so.1.0)
>==16039==    by 0x3B9D7A1A2F: (within /usr/lib64/libpython2.4.so.1.0)
>==16039==    by 0x3B9D7A1DEF: (within /usr/lib64/libpython2.4.so.1.0)

If you ran this against libpython with the debug symbols still in it, it would be
more meaningful. Usually, these are easy to fix when you see the function calls.
I'd build python again and try to run your script against python in the build dir
since that should still have the debug symbols. (You can use nm to verify.)
LD_PRELOAD might be used to load libpython from the builddir, too.

Without debug symbols, valgrind only tells you there's a problem - but not where
to fix it.

-Steve

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com