|
From: Yeshurun, M. <mei...@in...> - 2005-07-21 12:52:12
|
I had the same problem. It's no big deal, I kept multiplying by 10 until it worked. I also had to increase another constant - the number of segments (#defined near VG_N_SEGNAMES, don't remember the exact name). Perhaps these constants should be increased in the released version. Regards, Meir -----Original Message----- From: val...@li... [mailto:val...@li...] On Behalf Of Christoph Bartoschek Sent: Thursday, July 21, 2005 3:33 PM To: val...@li... Subject: [Valgrind-users] AMD64 and memory Hi, Someone mentioned that with --enable-pie one can use more memory on AMD64=20 than 1.5GB. Is this correct? However I tried this and it goes further thant without --enable-pie and uses=20 3.5GB when it stops with the following message: coregrind/m_aspacemgr/aspacemgr.c: VG_N_SEGNAMES is too small: increase it and rebuild Valgrind. coregrind/m_aspacemgr/aspacemgr.c: giving up now. What would be a reasonable value for this constant? Should I also increase the=20 other constants in this file? Christoph ------------------------------------------------------- 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 |
|
From: Yeshurun, M. <mei...@in...> - 2005-07-22 13:22:48
|
Hi, What does this --enable-pie flag supposed to do? I tried it, Valgrind doen't even accept this flag. Thanks, Meir -----Original Message----- From: val...@li... [mailto:val...@li...] On Behalf Of Christoph Bartoschek Sent: Thursday, July 21, 2005 3:33 PM To: val...@li... Subject: [Valgrind-users] AMD64 and memory Hi, Someone mentioned that with --enable-pie one can use more memory on AMD64=20 than 1.5GB. Is this correct? However I tried this and it goes further thant without --enable-pie and uses=20 3.5GB when it stops with the following message: coregrind/m_aspacemgr/aspacemgr.c: VG_N_SEGNAMES is too small: increase it and rebuild Valgrind. coregrind/m_aspacemgr/aspacemgr.c: giving up now. What would be a reasonable value for this constant? Should I also increase the=20 other constants in this file? Christoph ------------------------------------------------------- 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 |
|
From: Tom H. <to...@co...> - 2005-07-22 13:40:04
|
In message <942...@ha...>
Meir Yeshurun <mei...@in...> wrote:
> What does this --enable-pie flag supposed to do? I tried it, Valgrind
> doen't even accept this flag.
It's an option to configure when you build valgrind. It causes it to
be built as a position independent executable so that it can be loaded
anywhere in the address space instead of at a fixed position.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Yeshurun, M. <mei...@in...> - 2005-07-22 14:15:31
|
I got
relocation can not be used when making a shared object; recompile with
-fPIC
What should I do?
Thanks,
Meir
-----Original Message-----
From: val...@li...
[mailto:val...@li...] On Behalf Of Tom
Hughes
Sent: Friday, July 22, 2005 4:40 PM
To: val...@li...
Subject: Re: [Valgrind-users] AMD64 and memory
In message
<942...@ha...>
Meir Yeshurun <mei...@in...> wrote:
> What does this --enable-pie flag supposed to do? I tried it, Valgrind
> doen't even accept this flag.
It's an option to configure when you build valgrind. It causes it to
be built as a position independent executable so that it can be loaded
anywhere in the address space instead of at a fixed position.
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
|
|
From: Tom H. <to...@co...> - 2005-07-22 14:23:05
|
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="-fpie" when you are
building vex or vex won't be position independent and won't be able
to be linked into valgrind.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
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
|