Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!apple!netcom!dlb!shawn!root
From: root@shawn.uucp (0000-Admin(0000))
Newsgroups: comp.windows.x
Subject: Re: X11 on HP-UX 7.0 -- what I fixed in XtRealloc()
Message-ID: <1991Jan28.063829.161@shawn.uucp>
Date: 28 Jan 91 06:38:29 GMT
Reply-To: root@shawn.uucp (Admin)
Distribution: usa
Organization: The Vampire Lestat
Lines: 16

My mailer is brain-dead, so I thought I'd post the response to inquirers
since others could benefit.

I was asked what I debugged in XtRealloc() to get X11R4 working on HP-UX 7.0:

Basically, as best as I can remember, XtRealloc() failed and printed an error
to stdout whenever it was given a size argument of zero.  As I recall,
realloc() should free the block in question at that point (at least on some 
systems).  I manually hacked XtRealloc.c so that if a size of zero was ever 
passed in, it would invoke free() on the block pointed to instead of realloc().
After that, all the Toolkit clients that were malfunctioning before began to
work correctly.

My guess is that realloc(2) had a subtle change between HP-UX 6.5 and 7.0,
since 1) X11R4 is advertised to compile "off-the-shelf" on 6.5 and
2) everything else seems just fine on 7.0.