Is libiostream broke in Solaris 10?

Question

The following code:
------cut--------------------------------------------------------------------------
#include <stdio.h>
#include <stdlib.h>
#include <sys/types.h> // use of getpid
#include <unistd.h> // use of getpid
#include <signal.h>
#include <sys/param.h>
#include <sys/termios.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <errno.h>
#include <iostream.h> // use of ostream
#include <strstream.h> // use of strstream
//static ostrstream os;
void printPid()
char tmp[100];
ostrstream os(tmp,100);
os << getpid() <<ends;
cout << "pid is "<< os.str() <<endl;
return;
main()
while(1)
printPid();
exit(0);
-------------cut---------------------------------------------------------------
works fine in Solaris 8 (compiled with WS6U2) but leaks memory (actually keeps growing) when run in Solaris 10. It looks like libiostream.so.1 is broke or incompatable.
Are we doing something wrong. Any and all help appreciated.
Thanks in advance.
-- prasad

Answer 1

We have tried both i.e.
1) built the executable on Solaris 8 with WS6U2 and ran it on Solaris 10
2) built the executable on Solaris 10 with Studio 10 and ran it on Solaris 10
Here's the exact command we are using to build this program: (similar to what we do in our Makefile so there maybe some redundancy)
$CC -DRW_NAMESPACE_REQUIRED -features=extensions -w -xprefetch=yes -g -I. -D_REENTRANT -DSOLARIS -DSIGNAL_ARGS -c -o getPid.o getPid.C
$ CC -g -i -Qoption ld -i -DRW_NAMESPACE_REQUIRED -library=rwtools7,iostream -features=extensions -R$ORIGIN/../lib getPid.o -Llib -lrt -lnsl -lsocket -o getPid
History:
We are in the process of migrating our huge code (>1M lines & mostly C++) to Solaris 10 and Studio 10 and that's when we have started noticing huge memory footprints in some of our executables. We have used ::findleaks to and DTrace to narrow it down to libiostream. We are currently building the code in parallel on both Solaris 8 (with WS6U2) and Solaris 10 (Studio 10). Our code works fine on Solaris 8 but has problems on Solaris 10. I have posted some of the memory leak details at:
http://www.opensolaris.org/jive/forum.jspa?forumID=4
the thread is titled "mdb: findleaks: requires UMEM_DEBUG=audit or"
-- prasad