Re: [Texmacs-dev] GCC 3.2 segfaults...

[Joris van der Hoeven]

> The test described in my previous mail shows the same behaviour, i.e. some 
> tree object
> must have been deleted more than once.
> 
> I'm unable to reproduce this in non-optimized build. Also the bug seems to be 
> unrelated
> to auto_save (i.e. reproducible without).
> 
> Anyone have any ideas?

Well, all this looks very much to what I experienced with g++-3.0 :v(100x(
If a tree gets deleted more than once, then this is probably due to
the compiler (whence an agrravation if you use optimization) and
the same bug is likely to occur at *several* and *random* places
in the code (whence its possible appearance independently from auto-save).
If the bug is really this double-destruction bug, then I see three possible 
fixes:

  1) Finding a way to quickly trace down the routines where objects get
     destroyed twice and make "no-op changes" to the code which make
     the compiler obtemperate. This is only possible if the bugs occurs
     at a few places (this is likely, because many other people would have
     complained otherwise).

  2) Support Hans Boehme's gc. This solves the problem for most pointer
     objects whose destructors would become no-ops. However, there will
     still be some destructors left which should do something. If we are
     unlucky, then this aproach will not eliminate all bugs.

  3) Wait for the g++ guys to do their job.

> Anyway, everyone using GCC-3.2 should be advised to use GCC-3.2 older than 
> 20021029
> to eliminate a very obscure bug with destructors. Or wait for GCC-3.2.1 which 
> should be
> released in a couple of weeks.

And which, hopefully, does eliminate this bug :^\=\