The proposed patch is obsolete now, since the real root of the problem
seems to be fixed now.
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live we
>
> Neat trick - thanks! I've found the problem - in lines 661 to 664 of
> tower.cxx we check if t is the user, but then dereference the AI plane
> pointer of tt based on the result. In the case where t is not the user, but
> tt is the user, the AI plane pointer dereference ( ->GetLeg() ) kill
Thanks a lot David for taking care of it.Julien
Ok, I think this bug should be fixed in CVS now - it was a typo after all that.
Whenever an AI plane was asked to follow the user whilst the user was flying a
circuit approach, the sim crashed. Since most of my recent testing has
happened to use straight-in approaches, I wasn't triggering it.
"Julien Pierru" writes:
> David i had the same problem with gdb and SDL so someone on IRC told me to
> use gdb attach [process ID]and then type c after you launch fgfs outside
> gdb, that way even if the screen locks up you can switch to another virtual
> console and look at the backtrace. That's
David Luff wrote :
> "Olaf Flebbe" writes:
>
>
>> Melchior told me about it and I was able to reproduce it once. I had
>> to increase AI traffic and starting at KSJC (San Jose)
>>
>> I investigated it a lot and it seems to me that two AI Aircrafts have
>> been introduced with the same callsign.
David i had the same problem with gdb and SDL so someone on IRC told me to use gdb attach [process ID]and then type c after you launch fgfs outside gdb, that way even if the screen locks up you can switch to another virtual console and look at the backtrace. That's how i got the one at the top of t
"Olaf Flebbe" writes:
> Melchior told me about it and I was able to reproduce it once. I had
> to increase AI traffic and starting at KSJC (San Jose)
>
> I investigated it a lot and it seems to me that two AI Aircrafts have
> been introduced with the same callsign. (maybe one with the current
> p
Melchior told me about it and I was able to reproduce it once. I had
to increase AI traffic and starting at KSJC (San Jose)
I investigated it a lot and it seems to me that two AI Aircrafts have
been introduced with the same callsign. (maybe one with the current
player callsign) Deleting one of the
"Julien Pierru" writes:
> The bug occured with CVS/HEAD. I was using ATC and AI traffic of 2. I tried
> flying from both KHAF and KSFO. Both of these airports resulted in the
> crash.
Thanks! I'll try and reproduce it now...
Cheers - Dave
--
"Julien Pierru" writes:
> The bug occured with CVS/HEAD. I was using ATC and AI traffic of 2. I tried
> flying from both KHAF and KSFO. Both of these airports resulted in the
> crash.
Thanks! I'll try and reproduce it now...
Cheers - Dave
--
The bug occured with CVS/HEAD. I was using ATC and AI traffic of 2. I tried flying from both KHAF and KSFO. Both of these airports resulted in the crash.Regards, Julien
"Julien Pierru" writes:
> Following is a backtrace of a segfault.
> It concerns AIPlane and was originally reported by decadix in January, but
> here it is:
>
> Program received signal SIGSEGV, Segmentation fault.
> < ... >
> It happened when i tried to land at KOAK behind an AI plane, and i wa
Following is a backtrace of a segfault.It concerns AIPlane and was originally reported by decadix in January, but here it is:Program received signal SIGSEGV, Segmentation fault.[Switching to Thread -1225357600 (LWP 7499)]
0x080c911c in FGTower::ProcessDownwindReport (this=0xc14b638, t=0xd8ba038) at
14 matches
Mail list logo
