|
From: Bart V. A. <bar...@gm...> - 2009-05-11 14:05:11
|
On Mon, May 11, 2009 at 3:22 PM, Naveen Kumar <g_n...@ya...> wrote: > I did some more testing and that LDFLAGS="-L$(TARGET_LIB_PATH)" was the culprit. I removed that for the cross compilation and valgrind starts up fine on target now. Just FYI I did nm on the new executable and there are still undefined symbols > > U __assert_fail@@GLIBC_2.0 > [ ... ] The symbols you listed are all defined in glibc. So undefined symbols probably only cause a segmentation fault on PPC if these are not defined in any shared library that is loaded during startup. And it's good to hear that Valgrind now runs fine ! Bart. |