https://bugs.kde.org/show_bug.cgi?id=339605
--- Comment #7 from Paul Floyd <pjfl...@wanadoo.fr> --- Indeed. I've been tryiing to slowly clear out some old bugzilla items. Normally the way that valgrind works is that valgrind is a small stub exe that just execs the tool (I'll use helgrind as an example). helgrind doesn't link with libc and doesn't even have a main(). It just has an assembler _start. It bootstraps itself out of the way of the memory that the guest gets loaded into. Then to start the guest it sets LD_PRELOAD for the core and helgrind preload dynamic libs, loads ld.so and the guest exe and starts running the ld.so code in the Valgrind VM. Normally the undefined symbols in the preload helgrind lib will be satisfied by the guest exe, either directly or indirectly. If this is no longer an issue, can I close it? -- You are receiving this mail because: You are watching all bug changes.
