| Summary: | SIGSEV when the tested application execl() applications with LD_PRELOAD | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | kimelto |
| Component: | general | Assignee: | Julian Seward <jseward> |
| Status: | REPORTED --- | ||
| Severity: | crash | CC: | stas |
| Priority: | NOR | ||
| Version: | 3.6 SVN | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
The same problem happens on FreeBSD as well, and it seems it is cause by valgring trying to write to the data, referenced by envp, which appears to be write-protected. It happens in the mash_colon_env function when it tries to get rid of unwanted env variables. One of the solutions might be to create a copy of the env string before passing it to the mash_colon_env function, and reset the env value to a new string if the function modified it. |
Version: 3.6 SVN OS: Linux When the application that we want to test with valgrind use the LD_PRELOAD environment variable, valgrind crash when the application call an other process. Reproducible: Always Steps to Reproduce: Write an application which putenv("LD_PRELOAD=whatever.so"); and call an external application with execl() functions. Run this application through valgrind. Actual Results: --7687-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --7687-- si_code=2; Faulting address: 0x804C0CB; sp: 0x62ae7c84 valgrind: the 'impossible' happened: Killed by fatal signal ==7687== at 0x38029B9D: mash_colon_env (m_libcproc.c:195) ==7687== by 0x38029D31: vgPlain_env_remove_valgrind_env_stuff (m_libcproc.c:254) ==7687== by 0x3807225E: vgSysWrap_generic_sys_execve_before (syswrap-generic.c:2596) ==7687== by 0x380675E0: vgPlain_client_syscall (syswrap-main.c:1442) ==7687== by 0x38063927: handle_syscall (scheduler.c:885) ==7687== by 0x38065402: vgPlain_scheduler (scheduler.c:1081) ==7687== by 0x38096A34: run_a_thread_NORETURN (syswrap-linux.c:94) Expected Results: A valgrind report.