https://bugs.kde.org/show_bug.cgi?id=445607
--- Comment #3 from Paul Floyd <pjfl...@wanadoo.fr> ---
If I increase the brk segment from 8M to 1G that part of the message goes away,
but the other parts remain.
The diff to do that is
diff --git a/coregrind/m_initimg/initimg-freebsd.c
b/coregrind/m_initimg/initimg-freebsd.c
index d19186a42..59c2f4f85 100644
--- a/coregrind/m_initimg/initimg-freebsd.c
+++ b/coregrind/m_initimg/initimg-freebsd.c
@@ -891,7 +891,7 @@ IIFinaliseImageInfo VG_(ii_create_image)( IICreateImageInfo
iicii,
//--------------------------------------------------------------
{
SizeT m1 = 1024 * 1024;
- SizeT m8 = 8 * m1;
+ SizeT m8 = 8 * m1 * 128;
SizeT dseg_max_size = (SizeT)VG_(client_rlimit_data).rlim_cur;
VG_(debugLog)(1, "initimg", "Setup client data (brk) segment\n");
if (dseg_max_size < m1) dseg_max_size = m1;
Note that questions about this arise frequently. This has to be hard coded as
it is really early in the tool startup, and it is not yet possible to parse
command line arguments or read environment variables.
--
You are receiving this mail because:
You are watching all bug changes.
