🚀 go-pugleaf

For some reason, a call to sprintf() instead one of my routines
(called getTempName()) hangs my PM application (using C-Set/2 from
CD ROM to compile).

Since sprintf() calls malloc() I decided to allocate 100 bytes before
calling sprintf() (and immediately free the 100 bytes), and - sure enough -
the app hung on the malloc() call.

It sounds like something is getting trashed somewhere, but I don't make
any calls to malloc() (I use my own home-grown routines, which I am 99%
sure are correct) so it's not like the run-time is suffering from memory
fragmentation.

If *anyone* has any ideas what's going on, *please* let me know, since this
is a "show stopper."

Cheers,
Q
-- 
"If you choose not to decide, you  | "A fool and his money are fun to go
 still have made a choice" - Rush  |  out with" - seen on a T-shirt
------------------------------------------------------------------------