Re: [Texmacs-dev] [PATCH] solves GCC 3.2 auto_save segfault for me...

[Igor V. Kovalenko]

Joris van der Hoeven wrote:
> > > What is surprising, is that the patch you proposed does seem to eliminate
> > > the bug on your system. Please check well though, because I did notice
> > > some change in the behaviour of TeXmacs. For instance, TeXmacs does not
> > > automatically crash at the first autosave, but only after typing a bit.
> > > You may also try to add a line "rep = NULL" at the end of destroy_tree_rep
> > > in order to check whether this also stabilizes TeXmacs on your system...
> > >
> > > In fact, the bug seems to be related to some kind of memory corruption.
> > > Another approach might be to determine which memory location
> > > is corrupted and then try to track down where in the code this happens.
> > > It may be some very dumb compilation error in some not-too-often used routine.
> > > I do not know any debugging tool which allows you to do this though.
> >
> > I'll dig into this.
>
>
> Another interesting to try might be to let delete and delete[] become no-ops.
> Of course, your computer is recommended to have some more memory in that case,
> but it will learn us whether the bug is due to wrong memory management or
> an error in the g++ compiler/optimizer concerning destructors.

I'll also give this a try in a couple of days...

Now concerning memory requirements.
During valgrind'ifying you wan't beleive the process consume about 320 Mb for 
140k
TeXmacs file. No problem here. It's just too sloooow... most of memory accesses 
are tagged.

BTW I've implemented destructor memory poisoning, but this still needs checking 
as there
is no sign of error...

--
Regards,
Igor V. Kovalenko    mailto: iko at crec dot mipt dot ru