https://bugs.kde.org/show_bug.cgi?id=508638
--- Comment #1 from Paul Floyd <[email protected]> --- No problem on Linux. ${HOME}/tools/valgrind/bin/valgrind --sim-hints=enable-outer --trace-children=yes \ --smc-check=all-non-file \ --run-libc-freeres=no --tool=none -q \ ./vg-in-place --vgdb-prefix=./inner --tool=none -q true ^^^ runs without a squeak A while back I did increase the FreeBSD memory space from 32Gb to 128Gb 35bb01dd450bfe3ba658ec5b58bc9f47dfc4c2aa FreeBSD: make amd64 aspace max mem 128Gbytes Also this diff 78a7f9244163bd6dba3b556f3708269a49a59243 FreeBSD: clean up guest stack creation code - - suggested_clstack_end = aspacem_maxAddr - (kern_maxssiz - kern_sgrowsiz) + VKI_PAGE_SIZE; + VG_(printf)("maxssiz %lx\n", kern_maxssiz); + //suggested_clstack_end = aspacem_maxAddr - (kern_maxssiz - kern_sgrowsiz) + VKI_PAGE_SIZE; #endif + // on amd64 we have oodles of space and just shove the new stack somewhere out of the way + // x86 is far more constrained, and we put the new stack just below the stack passed in to V + // except that it has stack space and the growth stack guard below it as decribed above + // so we need to skip over the existing stack/growth area on x86 + +# if VG_WORDSIZE == 4 suggested_clstack_end = aspacem_maxAddr - 64*1024*1024UL + VKI_PAGE_SIZE; - #else - suggested_clstack_end = aspacem_maxAddr - 16*1024*1024UL - + VKI_PAGE_SIZE; - + suggested_clstack_end = aspacem_maxAddr; #endif -- You are receiving this mail because: You are watching all bug changes.
