Leonardo Rochael Almeida wrote: > On Wed, 2002-03-13 at 13:04, Shane Hathaway wrote: > >>I just found out about something that might help. If you compiled >>against the GNU C library, you can set the environment variable >>MALLOC_CHECK_ to 1 to get malloc usage warnings printed to stderr, or >>set it to 2 to cause an abort() as soon as an error is detected. >>Assuming you're running in production, I'd start with 1 (making sure >>stderr is connected to something), then if any warnings occur but they >>aren't informative enough, switch to 2. >> >>I learned this here: >> >>http://www.gnu.org/manual/glibc-2.2.3/html_node/libc_32.html >> > > Thanks Shane, I'll try that. But first I need a way to not supply -D and > still get the stderr redirected. This site uses cookie authentication > (exUserFolder) and even though the traceback ends up in a page that is > shortly redirected from, some of our client's customers can spot it > sometimes and they usually call complaining about "the Zope error they > saw imediatelly before the login page" so we had to disable '-D'.
-D is actually not related AFAIK. The C library will output to stderr regardless of whether -D is supplied, which means you need to use standard redirection anyway, for example: ./start >/var/local/log/zope_output 2>&1 Shane _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
