Path: utzoo!attcan!uunet!ns-mx!iowasp.physics.uiowa.edu!ceres.physics.uiowa.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!unmvax!uokmax!d.cs.okstate.edu!minich
From: minich@d.cs.okstate.edu (MINICH ROBERT JOHN)
Newsgroups: comp.sys.mac.programmer
Subject: Help me port UNIX to THINK C 4.0
Message-ID: <1990Jul31.104414.16305@d.cs.okstate.edu>
Date: 31 Jul 90 10:44:14 GMT
Sender: minich@d.cs.okstate.edu (Robert Minich)
Organization: Oklahoma State University, Stillwater
Lines: 28


  I'm trying to port Rayshade 3.0 to my Mac (SE/30) and am having
strange difficulties. I've managed to get all the code compiled OK with
minor alterations (the project file is ~700K and the final app ~160K)
but I am running into problems with malloc(). Although I have given
plenty of memory to the partition (under the debugger and as a stand
alone app), malloc() goes off into deep thought and never exits. This
happens after a few successful malloc()'s, so something is working
right. Under MacsBug, I can see that my programs routines are being
called (ie, I see the labels when I crawl the return addresses on the
stack) but malloc() calls something unknown, which I suspect is library
code of some sort. 
  If it makes a difference, the problem occurs in a parsing routine
(courtesy of yacc/lex from a UNIX machine) trying to apparently copy a
string to somewhere useful. I'm using the ANSI-881 library with 68881
code generation turned on (non-FPU code in some files was twice the
size!) and I'm using the console library, at least until I get the thing
to run successfully.
  If anyone has experience with malloc() problems or suggestion as to
where to bang my head into concrete, please let me know. It's very
discouraging to have this much code compile but die on something as
common as malloc. Ugh.

-- 
|_    /| | Robert Minich            |
|\'o.O'  | Oklahoma State University| There are no heroes --
|=(___)= | minich@a.cs.okstate.edu  |   We all wear gray hats.
|   U    | - Ackphtth               |