Re: [Valgrind-users] Need for help : to prevent valgrind from terminating due to SIGSEGV

[Alexander P. <gl...@go...>]

> #0  0x04009a34 in _vgr20210ZU_libcZdsoZa_memset (s=0x0, c=0, n=22150000) at
> mc_replace_strmem.c:1007
This line clearly denotes that for some reason memset(0, 0, 22150000)
is being called.
You can insert assert(first_parameter_of_memset) before that line in
order to make sure it is (or is not) NULL.
Most probably this is a bug in your code - in this case Valgrind can't
fix it for you.
Recovering from SIGSEGV is a tricky thing which is not what most
people ever need.

--
Alexander Potapenko
Software Engineer
Google Moscow