Thanks Emeric:-)
On Fri, Jan 18, 2013 at 4:15 AM, Emeric VIGIER wrote:
> Manjeet,
>
> That's interesting... I am not quite sure 'free' and 'proc/mem/info'
> include any sensitive information for your company.
> If you stored your last sales figures in those files, believe me, it is a
> wrong
Manjeet,
That's interesting... I am not quite sure 'free' and 'proc/mem/info'
include any sensitive information for your company.
If you stored your last sales figures in those files, believe me, it is a
wrong wrong idea...
Also it is probably against your company policy to expose your problems on
@Emric...I would have do that , but I am sorry I can't do
anything against of company policy...
But u can do @ ur side...
Write a simple program and do malloc and memset in while(1) , it will give
u OOM (if u have enabled it or if u have applied OOM patch)...
then you can checkout all the informa
Can you make a print of what returns "free" command and /process/meminfo?
It would help us target our answer to your specific example.
Emeric
Le 17 janv. 2013 04:10, "Manjeet Pawar" a écrit :
> Hi all,
>
> I have a issue regarding memory .
>
> I ran a program on my board that continuously do mal
Hi all,
I have a issue regarding memory .
I ran a program on my board that continuously do malloc and write some data
at that memory location and put this code in while loop. it ran for some
time untill it consume the whole of the memory and then given a OOM. where
we get information about the me
