Re: Valgrind Internal Error: Valgrind received a signal 11 (SIGSEGV) - exiting
John Reiser <[email protected]>
| Newsgroups | gmane.comp.debugging.valgrind |
|---|---|
| Message-ID | <[email protected]> |
> I am receiving a valgrind Internal error upon startup of a multi-threaded application. It appears to be related to the option track_origins as I was not seeing the issue without the track_origins option. I am using the following valgrind options: --trace-children=yesand --track-origins=yes. Please tell us the following essential information: 0. You claim "a multi-threaded application" yet valgrind says "Command: /bin/touch ...". Explain. [Is it implemented via busybox?] 1. Confirm that the machine architecture is 32-bit ARM. (The string "memcheck-arm-linux" appears in the output.) 2. What is the make and model of the machine? Is it a virtual machine, or real hardware? 3. How much physical RAM? How much swap space? (The string "out_of_memory" appears in the output.) 4. Was valgrind essentially the only process running? 5. How many threads? 6. Run without --trace-children=yes, then copy+paste here the HEAP SUMMARY and LEAK SUMMARY paragraphs. 7. What is the approximate allocation profile? A zillion little blocks, or a few very large blocks, etc? 8. Which linux distribution and version? 9. Run "readelf --segments the_executable" and copy+paste here the output. 10. When the internal error happens (or shortly before), what does "ps -l" say about the process?