[dpdk-dev] [PATCH] eal: add madvise to avoid dump memory

Burakov, Anatoly anatoly.burakov at intel.com
Wed Apr 22 11:53:23 CEST 2020


On 22-Apr-20 4:13 AM, Li Feng wrote:
> Really?So weird.
> I have tested on 4 machines, running CentOS 7.
> The core dump size is the same as the first argument GiB.
> 
> Thanks,
> 
> Feng Li
> 
> Burakov, Anatoly <anatoly.burakov at intel.com> 于2020年4月22日周三 上午1:02写道:
>>
>> On 21-Apr-20 5:38 PM, Feng Li wrote:
>>> Hi Anatoly,
>>>
>>> This program could run like this:
>>> gcc test_map.c
>>> ./a.out 2 &
>>> gcore `pidof a.out`
>>>
>>> You will get a core dump sized to 2GiB.
>>>
>>> Thanks,
>>> Feng Li
>>>
>>
>> I did just that, and my core dump was ~100K in size. Hence my asking
>> about any special configuration required.
>>
>> --
>> Thanks,
>> Anatoly
> 

Apologies, i've looked at the wrong core dump file. I do get a 2G core 
dump out of it.

However, i've added madvise call for that memory and run the exact same 
command line you gave me, and i can see multiple core dump files, some 
of them are 2G files. Does that mean that MADV_DONTDUMP doesn't work?

-- 
Thanks,
Anatoly


More information about the dev mailing list