On Jan 21, 2008 12:51 PM, Torsten Dreyer wrote:
> Am Montag, 21. Januar 2008 18:21 schrieb Curtis Olson:
> > I am testing the udp version of doing master/slave copies of FlightGear
> > here this morning. I'm doing this with a stock v1.0 version. So far
> > everything seems to be behaving well. I'm not seeing any rapid memory
> > leak, and so far no crash.
> >
> > Are you seeing this only with file I/O? Are you seeing this with
> network
> > I/O? How long do you need to have the system running before you see
> memory
> > thrashing or a crash?
>
> I get the segfault with file-io and a udp link.
> This is my environment:
> - SuSE Linux 10.3 running x86_64 on a Intel(R) Core(TM)2 CPU.
> - Two instances of FlightGear frame-rate-throttled to 25 fps each
> - FlightGear stock 1.0.0 build from source and current plib cvs built with
> gcc
> 4.2.1
Here's one possible difference, I'm running with plib-1.8.4 ... any chance
you could try that and see if it makes a difference. I realize a complete
ground up recompile is not trivial, but flightgear does leverage plib's low
level network code, so is it possible that a change in plib since v1.8.4 is
causing us grief?
The native_ctrls issue you point out is a surprise to me, but as I look in
the cvs web browser pages, I see that Erik Hofman's name is attached to
these, and the specific commit was adding some new fields to the structure.
I think it makes sense to remove the comments that disable network byte
order. That appears to have been a mistake that slipped through the cracks.
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
