Hello,

I am debugging a C++ application that was ported from PostgreSQL to
DB2 UDB (v8.1.0.112) on Linux and have run across a problem.  We have
a singleton object that handles connection pooling, creating
connections, etc.  This object is declared static to ensure
destructors run before the program exits.  The problem occurs when our
destructors run as the program is exiting. They attempt to free up DB2
resources that DB2 apparently has already freed and we receive a
segmentation fault.

If I remove 'static' from the singleton object, all *seems* to be
well.  Can I depend on DB2 always freeing up all handles, connections,
etc before a program exits?  If not, is there a way I can prevent
their cleanup code from running, or delay it until after our static
destructors have executed?  Is the DB2 cleanup code run through it's
own static destructor, a signal handler or some other mechanism?

Thanks in advance for any help!

Donna Lenharth