home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.hp:10158 comp.unix.admin:4935
- Path: sparky!uunet!gatech!bloom-beacon!eru.mt.luth.se!lunic!sunic!seunet!abbaut!alindbac
- From: alindbac@aut.abb.se (Anders Lindbck)
- Newsgroups: comp.sys.hp,comp.unix.admin
- Subject: Re: Enormous core dumps
- Summary: big probgrams leads to big trouble.
- Message-ID: <1992Sep8.122518.28298@aut.abb.se>
- Date: 8 Sep 92 12:25:18 GMT
- References: <90018@hpunsca.canada.hp.com> <BtutDw.C8D@news.cso.uiuc.edu> <1992Sep4.163132.22011@ctp.com>
- Organization: THHS (krfc) tlps
- Lines: 15
-
- In article <1992Sep4.163132.22011@ctp.com> jmay@ctp.com (Jason May) writes:
- >
- >What kinds of problems can lead to processes crashing and leaving behind
- >huge (for example, we had a 50 megabyte one this morning) core files?
- >I know how to limit this with limit or ulimit, but I'd like to know
- >more about the events that can cause such core dumps to occur.
- >
- >Thanks for your help,
- >-Jason (jmay@ctp.com)
-
- Once I had a core dump of over 70M ! The disc was full to 100%.
-
- The problem was that I allocated some memory and then continued to do
- so in absurdum. Since the allocated memory also is part of the code dump
- the core file will be very big if you allocate to much memeory...
-