Re: [Texmacs-dev] Strange bug with C++

[David Allouche]

On Wed, Apr 30, 2003 at 01:40:11PM +0200, Joris van der Hoeven wrote:
> 
> > > > Also, exactly where does the segfault occur?
> > >
> > > During the destruction of ifstream.
> >
> > Maybe valgrind could be of some help here. There could conceivably be
> > a memory corruption bug somewhere else which causes a crash in that
> > destructor but cause no problem otherwise. Yes that is improbable.
> 
> Probably, some allocations for ifstreams are done with malloc and
> the destructions with delete[]. So I think that the bug comes from g++.
> 
> I think that I once have to remove the global destructors and
> let them be inherited by the classes. But let's leave this for later...

Just to be sure, you could compile a source tree configured with
--disable-fastalloc (double check that is the correct configure option
before doing it).

-- 
                                                            -- DDAA