> You may want to try running the process under valgrind. Thanks. I'm trying that but have been so far unable to get valgrind to report any problems within Python or our libraries before that message, just a couple things at startup which seem to occur before Python gets going: ==21374== Invalid read of size 1 ==21374== at 0x4C2DEA9: putenv (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==21374== by 0x400E71: append_env_vars (binary-wrapper-main.c:175) ==21374== by 0x4008CA: set_binary_wrapper_env (c-python-wrapper.c:58) ==21374== by 0x40168D: main (binary-wrapper-main.c:382) ==21374== Address 0x51d6a84 is 0 bytes after a block of size 52 alloc'd ==21374== at 0x4C2ACCE: realloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==21374== by 0x400E61: append_env_vars (binary-wrapper-main.c:173) ==21374== by 0x4008CA: set_binary_wrapper_env (c-python-wrapper.c:58) ==21374== by 0x40168D: main (binary-wrapper-main.c:382) ==21374== ==21374== Syscall param execve(envp[i]) points to unaddressable byte(s) ==21374== at 0x4EE7067: execve (in /lib64/libc-2.15.so) ==21374== by 0x4016AA: main (binary-wrapper-main.c:385) ==21374== Address 0x51d6a84 is 0 bytes after a block of size 52 alloc'd ==21374== at 0x4C2ACCE: realloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==21374== by 0x400E61: append_env_vars (binary-wrapper-main.c:173) ==21374== by 0x4008CA: set_binary_wrapper_env (c-python-wrapper.c:58) ==21374== by 0x40168D: main (binary-wrapper-main.c:382) Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4