Re: [[gtkmm] Destroying container problem]



On 12 Jul 2002, Jarek Dukat wrote:

> 
> Nonsense, if it was a memory overrun then compiler change from 2.95 to
> 3.1 would not solve the problem.
> 

Not necessarily true. Often different optimisation modes can show up or
hide pointer errors and different compilers produce different code. It
only takes one compiler to pack some spare space here and there and an out
by one pointer error can be made harmless.

It would be interesting to diff the machine code but probably too much
work. gcc 3.1 is in general a better compiler though so it is possible
that
2.95 had a bug in its' C++ compiler.

Nick 




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]