?bug? with new SVR2 malloc library

[R. Curtis Jackson]

I have a program that draws hierarchy charts and has to store an
amazing amount of info to do so (also I'm lazy and don't care how
much memory it uses; I hate bean-counting programs).  I malloc for
enough memory to draw a 25-page H-chart for starters (usually enough),
then realloc in extra 5-page increments thereafter until I run out of
memory.

Well, I *did* run out of memory; when trying to realloc for about
990000 bytes.  This shouldn't have happened and I knew it.  So I tried
everything under the sun and finally, out of desperation, took the
-lmalloc off the ld command-line.  You guessed it -- worked like a
charm for much larger chunks of memory.

a) Does anyone know of a bug in the new (optional) realloc?

b) Please reply via mail, I'll post the correct answer as a short
note when I find out.

c) DO NOT ask me for a copy of my program -- it is hardwired to a very
specific implementation and would NOT be useful as a general-purpose
chart drawer.  Besides, I would assume that you want the thing not
because you have been forced to draw H-charts but because you like to
do them, and I would then use your request to get a good laugh with
my buddies at happy hour.

First they uphold searches on an illegal warrant, then they raise the
drinking age to 21, then they ban happy hours and lady's nights (takes
effect Aug. 1 here in NC), now they're well on the way to a mandatory
seatbelt law here, too.  I just *can't* wait until they install the
closed circuit TV monitor in my apartment!!
-- 

The MAD Programmer -- 919-228-3313 (Cornet 291)
alias: Curtis Jackson	...![ ihnp4 ulysses cbosgd mgnetp ]!burl!rcj
			...![ ihnp4 cbosgd akgua masscomp ]!clyde!rcj