Home > Archive > Unix Programming > July 2006 > long time to dump core
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
long time to dump core
|
|
| madhusudan.hv@gmail.com 2006-07-19, 4:00 am |
| hi,
Can any body tell, under what scenarios a process might take huge
amount of time to dump core?
For example like 40 minutes.
In my case my application is losing the socket connections and after 40
minutes only it is dumping core.
regards,
Madhusudan
| |
| Paul Pluzhnikov 2006-07-19, 8:02 am |
| madhusudan.hv@gmail.com writes:
> Can any body tell, under what scenarios a process might take huge
> amount of time to dump core?
If the app itself has huge memory footprint, and the core is written
to a slow disk or over a wide-area network.
> For example like 40 minutes.
I've seen apps that took good 10 minutes to dump core.
Usually the app itself has a bug causing it run out of memory ...
> In my case my application is losing the socket connections and after 40
> minutes only it is dumping core.
It's not clear what "loosing the socket connections" means.
The 2 events ("loosing" and dumping core) may be only remotely
related.
Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.
| |
| Nils O. Selåsdal 2006-07-19, 7:01 pm |
| madhusudan.hv@gmail.com wrote:
> hi,
> Can any body tell, under what scenarios a process might take huge
> amount of time to dump core?
> For example like 40 minutes.
> In my case my application is losing the socket connections and after 40
> minutes only it is dumping core.
If the process has eaten all memory,and all of the swap space, your
system might start trashing and dumping the thus very huge core can
take that much time.
|
|
|
|
|