|
From: Peter Z. <pet...@do...> - 2006-04-30 13:29:22
|
Hi All, Can valgrind 3.1.1 be used on a kernel with CONFIG_VMSPLIT_3G_OPT? All it's doing for me is: $ valgrind Killed $ I did compile valgrind after the kernel change. Relevent kernel settings are: CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_VMSPLIT_3G is not set CONFIG_VMSPLIT_3G_OPT=y # CONFIG_VMSPLIT_2G is not set # CONFIG_VMSPLIT_1G is not set Thanks. -Peter. |
|
From: Julian S. <js...@ac...> - 2006-04-30 13:34:19
|
Sigh (this is becoming a FAQ following appearance of
CONFIG_VMSPLIT_3G_OPT). Yes you can.
In ./configure find this
case "${host_cpu}" in
i?86)
echo "$as_me:$LINENO: result: ok (${host_cpu})" >&5
echo "${ECHO_T}ok (${host_cpu})" >&6
VG_ARCH="x86"
valt_load_address_normal="0xb0000000"
valt_load_address_inner="0xa0000000"
;;
(assuming you're using x86) and change 0xb0000000 to 0x30000000
(ignore the _inner). Let us know whether it works or not. If you're
using amd64 or ppc32 change the relevant entry for that arch
instead.
J
|
|
From: Peter Z. <pet...@do...> - 2006-04-30 13:46:59
|
On Sun, 30 Apr 2006 14:33:59 +0100
Julian Seward <js...@ac...> wrote:
> Sigh (this is becoming a FAQ following appearance of
> CONFIG_VMSPLIT_3G_OPT). Yes you can.
>
> In ./configure find this
>
> case "${host_cpu}" in
> i?86)
> echo "$as_me:$LINENO: result: ok (${host_cpu})" >&5
> echo "${ECHO_T}ok (${host_cpu})" >&6
> VG_ARCH="x86"
> valt_load_address_normal="0xb0000000"
> valt_load_address_inner="0xa0000000"
> ;;
>
> (assuming you're using x86) and change 0xb0000000 to 0x30000000
> (ignore the _inner). Let us know whether it works or not. If you're
> using amd64 or ppc32 change the relevant entry for that arch
> instead.
>
> J
Yes it works fine, thanks. I even greped from c0000000, since that
seems to be the default PAGE_OFFSET, I guess I didn't quite get it.
-Peter.
|