Message-Id: <199608300423.AAA28326@breckenridge.openmarket.com>
To: fastcgi-developers@OpenMarket.com
Subject: Re: FastCGI with Purify
In-Reply-To: <199608292209.SAA13022@bill-graham.nfic.com>
Date: Fri, 30 Aug 1996 00:23:40 -0400
From: Mark Brown <mbrown@OpenMarket.com>
Bob Ramstad asks:
how does one go about using Purify with FastCGI? i haven't had
much success using the two together --- i'd like to run the Purified
executable via a web browser, so i can easily run through the various
functions of the FastCGI executable, but whenever i hook this up, i
get "FastCGI terminated... due to exit" all over the place.
What I've done is to direct all of the Purify output to a log file, by
building with something like:
CC_PURE = /usr/local/pure/purify-3.2-solaris2/purify \
-log-file=/udir/mbrown/sample-store.plog \
-always-use-cache-dir -cache-dir=/udir/mbrown/purify \
-inuse-at-exit=yes -leaks-at-exit=yes \
-fds-inuse-at-exit=yes cc
I've had nothing but good experiences with Purify and FastCGI
on Solaris. You may be running into some SunOS differences.
When debugging you should abort rather than exit when FCGI_Accept
returns failure, so you get a core dump and perhaps see what went
wrong.
The lack of accept retry on errno == EINTR could cause premature
exits if there are any signals coming into the process, so you
should apply the patch that went out yesterday.
--mark