On Thu, 18 Nov 1999 14:13:36 EST, Ilya Zakharevich wrote: >Gurusamy Sarathy writes: >> >I'm continuing to see this segmentation fault. The last suggestion from >> >the list was that I had PERL_DESTRUCT_LEVEL set to a value greater >> >than 2. But I don't have any such variable set in my shell variable >> >environment. Is there someplace within perl's configuration environment >> >where this might be set? >> >> The test harness enables PERL_DESTRUCT_LEVEL for all tests not >> known to leak scalars due to compile-time failures. If you're >> getting a test failure due to "Scalars Leaked", it means there >> is a new scalar leak somewhere. > >Nope. The test in question *already has* "we have a known leak" clause. Is the "we have a known leak" clause in a BEGIN block? That would make a difference if the test quits due to errors during compilation. Sarathy gsar@ActiveState.comThread Previous | Thread Next