|
From: Yeshurun, M. <mei...@in...> - 2005-07-22 15:25:17
|
Thanks, it worked better than before, but then I got, like Cristoph:
VG_(get_memory_from_mmap): newSuperblock's request for 1048576 bytes
failed.
VG_(get_memory_from_mmap): 224186560 bytes already allocated.
Sorry. You could try using a tool that uses less memory;
eg. addrcheck instead of memcheck.
Does anyone have any suggestions?
Thanks,
Meir
-----Original Message-----
From: val...@li...
[mailto:val...@li...] On Behalf Of Tom
Hughes
Sent: Friday, July 22, 2005 5:23 PM
To: val...@li...
Subject: Re: [Valgrind-users] AMD64 and memory
In message
<942...@ha...>
Meir Yeshurun <mei...@in...> wrote:
> I got
>
> relocation can not be used when making a shared object; recompile with
> -fPIC
>
> What should I do?
You probably need to specify EXTRA_CFLAGS=3D"-fpie" when you are=20
building vex or vex won't be position independent and won't be able
to be linked into valgrind.
Tom
--=20
Tom Hughes (to...@co...)
http://www.compton.nu/
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. =
http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclick
_______________________________________________
Valgrind-users mailing list
Val...@li...
https://lists.sourceforge.net/lists/listinfo/valgrind-users
|