On Jan 21, 2008 2:38 PM, Torsten Dreyer wrote:
> > g++ (GCC) 4.1.2 20070925 (Red Hat 4.1.2-33)
> >
> > So the problem could also be related to your newer version of gcc
> (perhaps
> > being more picky or more standards compliant.) Or there could be a libc
> > difference too.
> Yeah that's what I think, too. I assume a different implementation in the
> STL
> to be more precise: the std:vector<>.
> I don't think I like the idea to build a gcc 4.1.2 and rebuild FlightGear
> from
> source with that compiler but I would not be surprised, if the crash
> disappears that way.
>
> Which compilier is tpalinkas using?
>
The other thing that concerns me is that even with your patch, tpalikas is
reporting order depencies in the master/slave startup sequence and doing it
wrong results in a crash. Also some new double free errors when exiting.
The communication between master & slaves is UDP so there should be
absolutely no order dependencies in startup. Any machine should be able to
start (or restart) in any order without affecting the stability of the
system. Somehow the master must be sending garbage during startup and
crashing the slaves.
Regards,
Curt.
--
Curtis Olson: http://baron.flightgear.org/~curt/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
