|
From: galapogos <go...@gm...> - 2008-08-25 04:04:49
|
Hi, I have an executable that I've compiled with statically linked libraries. When running valgrind, it gives me errors even with just a simple "hello world" program. If I compile it dynamically though, these errors go away. Why does compiling it statically produce these error message? -- View this message in context: http://www.nabble.com/Valgrind-gives-errors-when-checking-statically-compiled-code-tp19137630p19137630.html Sent from the Valgrind - Users mailing list archive at Nabble.com. |
|
From: Paul F. <pa...@fr...> - 2008-08-25 15:17:35
|
Quoting galapogos <go...@gm...>: > > Hi, > > I have an executable that I've compiled with statically linked libraries. > When running valgrind, it gives me errors even with just a simple "hello > world" program. If I compile it dynamically though, these errors go away. > Why does compiling it statically produce these error message? Hi Can you check (with ldd) that the app is only linked to static apps? If by accident the app was linked with both static and dynamic libs, then I'd expect errors. Paul |
|
From: galapogos <go...@gm...> - 2008-08-26 06:33:26
|
Paul Floyd wrote: > > Quoting galapogos <go...@gm...>: > >> >> Hi, >> >> I have an executable that I've compiled with statically linked libraries. >> When running valgrind, it gives me errors even with just a simple "hello >> world" program. If I compile it dynamically though, these errors go away. >> Why does compiling it statically produce these error message? > > Hi > > Can you check (with ldd) that the app is only linked to static apps? If by > accident the app was linked with both static and dynamic libs, then I'd > expect > errors. > > Paul > I've just done that, and ldd reports that it is not a dynamic executable. -- View this message in context: http://www.nabble.com/Valgrind-gives-errors-when-checking-statically-compiled-code-tp19137630p19156547.html Sent from the Valgrind - Users mailing list archive at Nabble.com. |