home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.atari.st.tech
- Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!hanauma.jpl.nasa.gov!hyc
- From: hyc@hanauma.jpl.nasa.gov (Howard Chu)
- Subject: Re: My problems with MiNT
- Message-ID: <1992Nov12.074835.22639@elroy.jpl.nasa.gov>
- Sender: news@elroy.jpl.nasa.gov (Usenet)
- Nntp-Posting-Host: hanauma.jpl.nasa.gov
- Organization: SAR Systems Development & Processing, JPL
- References: <1dn9q7INNk52@aludra.usc.edu>
- Date: Thu, 12 Nov 1992 07:48:35 GMT
- Lines: 21
-
- In article <1dn9q7INNk52@aludra.usc.edu> baffoni@aludra.usc.edu (Juxtaposer) writes:
- > Using MiNT .95, with _just_ it running in the autofolder, from the
- >desktop I run CoNnect1.80 and I get one "pid 2 (GEM): malloc: out of memory"
- >and then the rest (about 11) are "pid 3 (CONNECT): malloc: out of memory"
- >except towards the end there is a "pid 3 (CONNECT): Bconmap: mapin failed".
- >
- > So does anyone know why I am getting all these failed mallocs?
-
- I would ignore those messages; as I recall from reading the source code (I
- noticed these messages a while ago myself) the reason is that when MiNT
- intercepts the Malloc system call, it first tries to execute the Mxalloc
- call which currently only exists in the TT's TOS. This call fails on any
- non-TT, which causes the "malloc: out of memory" message. Then MiNT calls
- the regular TOS Malloc routine, and that usually succeeds. Likewise for
- the Bconmap failure, that call also only exists on new TOS. (Of course, if
- you're actually running on a TT or with TOS 2.06 or 3.06, then I'd guess
- the failures are genuine... You didn't specify what machine you have.)
- --
- -- Howard Chu @ Jet Propulsion Laboratory, Pasadena, CA
-
- All true wisdom is conveyed in one-line witticisms.
-