On 10/21/04 at 12:19 PM Chris Metzler wrote:
Here's what I see from gdb . . .
snip
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 3690)]
0x080b0705 in FGTower::ProcessDownwindReport (this=0xd041ee8, t=0xd87d8c8)
at AIPlane.hxx:80
80
On Thu, 21 Oct 2004 09:06:14 -0500
David Culp [EMAIL PROTECTED] wrote:
Just downloaded a fresh CVS FlightGear and found that the AI code is
causing segfaults now. I'll recompile and run it through gdb. In the
mean time beware that some aircraft that set up AI scenarios by
default, like the
I'm getting segfaults that seem related to the AI subsystem. They occur
when I turn AI traffic on through the menu. They seem more frequent
as I turn the AI traffic density up from 1 to 3. But they don't occur
promptly upon start; instead, they almost always occur when I'm on final
for a
On 10/21/04 at 9:52 AM David Culp wrote:
I'm getting segfaults that seem related to the AI subsystem. They occur
when I turn AI traffic on through the menu. They seem more frequent
as I turn the AI traffic density up from 1 to 3. But they don't occur
promptly upon start; instead, they
On Thu, 21 Oct 2004 15:55:24 +0100
David Luff [EMAIL PROTECTED] wrote:
Uggh, that's me in the firing line then! I haven't added any features
or code to the AI-traffic system for quite a while, probably pre-0.9.5.
I thought I had all the bugs worked out, but it seems not :-( It's been
