Re: [Valgrind-users] valgrind stack problem

[Paul F. <pa...@fr...>]

>
> Are you sure you're not trying to allocate too much stuff onto the stac=
k?
> 3.2.1 allows you a max stack of 16M and you get to segfault after that.

Hi

[Julian - sorry for reply-to-sender, just noticed as the message was sent=
]

It's quite possible that we're over 16M. I'll look into that.

I just noticed another thing. If I use --sanity-check=3D3 I get

# --30200:0:aspacem  sync_check_mapping_callback: segment mismatch: V's s=
eg:
# --30200:0:aspacem  NSegment{file, start=3D0x8048000, end=3D0x9A40FFF,
smode=3DSmFixed, dev=3D65043, ino=3D2147487009, offset=3D0, fnIdx=3D1, ha=
sR=3D1, hasW=3D0,
hasX=3D1, hasT=3D0, mark=3D0, name=3D"/view/PFView/vobs/adms/ixl-dbg/sim/=
aut"}
# --30200:0:aspacem  sync_check_mapping_callback: segment mismatch: kerne=
l's
seg:
# --30200:0:aspacem  start=3D0x8048000 end=3D0x9A40FFF prot=3D5 dev=3D63 =
ino=3D12330004
offset=3D0
name=3D"/ccstores/viewstore_1/admsviews/pfloyd/PFView.vws/.s/00011/80000d=
2144ec700aaut"
# --30200:0:aspacem  sync check at m_aspacemgr/aspacemgr.c:2031
(vgPlain_am_get_advisory): FAILED
# --30200:0:aspacem
# --30200:0:aspacem  Valgrind: FATAL: aspacem assertion failed:
# --30200:0:aspacem    VG_(am_do_sync_check)
(__PRETTY_FUNCTION__,__FILE__,__LINE__)
# --30200:0:aspacem    at m_aspacemgr/aspacemgr.c:2031 (vgPlain_am_get_ad=
visory)
# --30200:0:aspacem  Exiting now.

Could this be related? It looks like this is due to the fact that I'm run=
ning
the test within ClearCase. No problem either here with valgrind 3.0.1.

A+
Paul