Re: 10MB Chunks of anonymous memory for each thread created from shared object



googlegroups@xxxxxxxxxxxxxxxxxx writes:

Does anyone have any how I can find out what these anonymous memory
pages are?

Run the program under gdb, set breakpoint on __mmap and __mmap64,
when hit type 'where' ?

I bet they are still coming from thread stack allocation,
probably due to a bug in libpthread ...

Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.
.



Relevant Pages

  • Re: slurping in binary data
    ... that I must figure out precisely why it is that I don't expect the bug ... However, the recursion always ... I recently investigated a bug where there were missing packets from the output files of one of my programs. ... Because those were the easiest things to check, they were also the first things I checked (despite direct orders from upper management that I was not supposed to "waste" any time investigating the "impossibility" that those input files were defective). ...
    (comp.lang.c)
  • Re: slurping in binary data
    ... that I must figure out precisely why it is that I don't expect the bug ... However, the recursion always ... there were missing packets from the output files of one of my programs. ... certain assumptions about the contents of the input files. ...
    (comp.lang.c)
  • Re: Python bug? Named parameters in recursive calls sometimes confuses python?
    ... > Isn't it possible that the code has just returned twice? ... down in the recursion, instead of reverting to the object ... a Python bug! ... (It's the pure Python version 0.8) ...
    (comp.lang.python)
  • Re: [PATCH] workqueue: not allow recursion run_workqueue
    ... works is not run orderly when recursion run_workqueue ... It's bug. ... So we should not allow workqueue trying to flush its own queue. ... struct workqueue_struct *wq; ...
    (Linux-Kernel)
  • Re: [PATCH 2/3] workqueue: not allow recursion run_workqueue
    ... works is not run orderly when recursion run_workqueue ... It's bug. ... So we should not allow workqueue trying to flush its own queue. ...
    (Linux-Kernel)