|
From: Jeremy F. <je...@go...> - 2003-12-23 02:03:41
|
On Mon, 2003-12-22 at 17:50, John Carter wrote: > I just pull a fresh version out and said "make" and then "make > install" and tried that, no difference. You need to do a "sh autogen.sh; ./configure" to regenerate all the Makefiles from their .am counterparts. > I suspect it is probably the weird version of gcc/ld that I'm using to > build my app rather than how valgrind is being built. > > I will try use the same gcc/ld to build my app as valgrind tomorrow. No, that stage2 readelf output is completely broken. I'm pretty sure the bug is in Valgrind's Makefiles. Valgrind shouldn't care about *how* your binary was generated, so long as it is within the valid client address range (which it is). Actually, could you send me the output of your "ld --verbose" and "coregrind/x86/stage2.lds"? J |