Okay, I'm currently rebuilding FlightGear without threading support to see
what that will do. I don't suspect the threading stuff in particular, but it
probably adds quite a bit to the compexity of the debug process. I have a few
days off (good friday and easter), so hopefully I can do some
On Friday 09 Apr 2004 8:46 am, Durk Talsma wrote:
That's interesting: Does anybody know how I turn off the AI traffic (other
that hacking the code). I tried browsing the commandline options but
couldn't find one there.
It's an option from the FlightGear menu ATC/AI. I'm afraid I have to do
Curtis L. Olson wrote:
Andy Ross wrote:
Durk Talsma wrote:
It looks like the crash is somewhere inside the AIMgr (judging from
stackdump
item #15), but since I'm still incredably unfamiliar with this part of
the
code, this might just be a wild guess.
Anyways, I hope that this is
Jonathan Richards wrote:
On Friday 09 Apr 2004 8:46 am, Durk Talsma wrote:
That's interesting: Does anybody know how I turn off the AI traffic
(other
that hacking the code). I tried browsing the commandline options but
couldn't find one there.
It's an option from the FlightGear menu
Frederic Bouvier writes:
Curtis L. Olson wrote:
As I understand it, the deadbeef thing is something ssg writes into
memory that it frees. Later if you try to traverse something that is
marked as deadbeef, you know you have a pointer to deallocated memory.
This is typically what
Hi Folks,
As mentioned a few days ago, it appears that flightgear either aborts, or
fails with a DEADBEEF assertion error after running for a somewhat longer
period (about 1 to two hours). So I tried and do some testing by running fgfs
from inside the gnu debugger. It aborted after about 1.5
Durk Talsma wrote:
It looks like the crash is somewhere inside the AIMgr (judging from stackdump
item #15), but since I'm still incredably unfamiliar with this part of the
code, this might just be a wild guess.
Anyways, I hope that this is useful debug information. Can others
confirm this?
On Friday 09 April 2004 01:47, Andy Ross wrote:
Durk Talsma wrote:
It looks like the crash is somewhere inside the AIMgr (judging from
stackdump item #15), but since I'm still incredably unfamiliar with this
part of the code, this might just be a wild guess.
Anyways, I hope that this is
Andy Ross wrote:
Durk Talsma wrote:
It looks like the crash is somewhere inside the AIMgr (judging from stackdump
item #15), but since I'm still incredably unfamiliar with this part of the
code, this might just be a wild guess.
Anyways, I hope that this is useful debug information. Can others
