Re: [Flightgear-devel] Re: Next FlightGear Release - upcoming.
Hi,You may try the patch (ATC.diff) I sent a few days ago. I would be interested if this would fix it. I wonder if you see any of the diagnostics . already known in the output.Olaf 2006/3/18, Chris Metzler [EMAIL PROTECTED]: On Fri, 17 Mar 2006 19:19:19 +0100Melchior FRANZ wrote: * Melchior FRANZ -- Thursday 09 March 2006 19:43: (A) tower.cxx/AI Probably not yet fixed, but it has become *very* rare. I'll keep Olaf informed next time it happens.I think it still happens to me on about one out of every 20approaches or so.Happened to me night before last.
Re: [Flightgear-devel] Re: Next FlightGear Release - upcoming.
David Luff wrote: Melchior FRANZ writes: OK, you've pricked my consciensce. I'll make a concerted effort to track that one down, since it's undoubtably one of mine :-( I thought it might have been fixed, since I haven't seen it since a couple of bug-fixes were added to that bit of code be someone, but I guess it seems not :-( It would be nice to be able to enable the intelligent AI by default, at least at level 1, for one of the next couple of releases. Am I right in thinking there might also be an issue with crashes at the point of the now clear of my airspace message? Could be. I experienced one of these last weekend, a few minutes after take-off. Have been running FG in gdb ever since, but it did not happen again. Nine --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: Next FlightGear Release - upcoming.
On Thu, 9 Mar 2006 22:07:08 -0500, Chris wrote in message [EMAIL PROTECTED]: On Thu, 9 Mar 2006 19:43:13 +0100 Melchior FRANZ wrote: * Curtis L. Olson -- Thursday 09 March 2006 17:59: 2. We need to aggressively hunt down any random crashes I'm aware of four crashes: I've experienced another that I don't think is classifiable in your list. It occurred for me in-flight, during a long flight; but AI traffic wasn't on and I wasn't monitoring ATC. I've been running FG ever since in gdb just in case; but haven't been able to reproduce it. Still trying. ..core dump setup? Core dumps are neat for backtrack those out-of-the-blue crashes. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: Next FlightGear Release - upcoming.
On Friday 10 March 2006 14:38, Melchior FRANZ wrote: * Melchior FRANZ -- Thursday 09 March 2006 19:43: (D) -1000 ft crash. Don't remember the exact message. Doesn't seem related to any special subsystem. Attempting to schedule tiles for bogus lon and lat = (-1000,0) This is a FATAL error. Exiting! triggered by FGTileMgr::schedule_needed(). Which process sets lon=-1000 and lat=0 and requests a tile for that? m. I'm able to trigger this error message quite consistently by enabling traffic manager/AImodels. If the first few AIModels that are required to be loaded are non-existent, FlightGear crashes with this error message (always reporting the same coordinates, as mentioned above). Sofare, I've only been able to make an educated guess that generating an error condition in the main thread before or at the time the tile loader is running triggers this message and a subsequent abort. I'm still in the dark what's actually going on (possibly triggered by setting errno). FWIW, once scenery loading is complete, the FlightGear main thread/ AIModels subsystem happily ignores the loading of non-existent AIModels, as desiged. Fixing this, or at least resolving the interaction between any error condition set by AIModels in the main thread and an abort in the tile loader thread is currently at my todo list. But as I mentioned above, I don't really have a clue right now. Cheers, Durk --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: Next FlightGear Release - upcoming.
Hi,2006/3/9, David Luff [EMAIL PROTECTED]: Melchior FRANZ writes: * Curtis L. Olson -- Thursday 09 March 2006 17:59: 2. We need to aggressively hunt down any random crashes I'm aware of four crashes: (A) tower.cxx /AI -- old, but very annoying. Happens occasionally. Very hard to reproduce. Olaf looked into it and advised me to add a debug message in my copy, but since then I had no problems. (Maybe I should commit that?;-)This bug basically makes long-distance flights impossible.OK, you've pricked my consciensce.I'll make a concerted effort to track that one down, since it's undoubtably one of mine :-(I thought it might have been fixed, since I haven't seen it since a couple of bug-fixes were added to that bit of code be someone, but I guess it seems not :-(It would be nice to be able to enable the intelligent AI by default, at least at level 1, for one of the next couple of releases. Am I right in thinking there might also be an issue with crashes at the point of the now clear of my airspace message?Melchior is refering to this #0 0x080c9996 in FGAIPlane::GetLeg (this=0x0) at AIPlane.hxx:80 cptf #1 0x080c1c3f in FGTower::ProcessDownwindReport (this=0xd6bedb8, t=0xddccce8) at tower.cxx:664 cptf #2 0x080c5e95 in FGTower::Respond (this=0xd6bedb8) at tower.cxx:521 cptf #3 0x080c9734 in FGTower::Update (this=0xd6bedb8, dt= 0.03) at tower.cxx:357 cptf #4 0x080a5372 in FGATCMgr::update (this=0xb371d90, dt=0.03) at ATCmgr.cxx:167 cptf One can really rely on ATC crashing at the right moment. ;-) (Somehow a plane occurs which contains no AI and is not ourselfs?) I did the changes you are refering to, because there were a couple of STL problems hidden. I may have broken something so I did some heavy investigations into that and the most plausible cause seems to me that planes with identical callsigns have been around. I introduced some prints, but the problem didn't trigger any more for me. The patch removes some unused code, too. ATC.patch Description: Binary data
Re: [Flightgear-devel] Re: Next FlightGear Release - upcoming.
On Thu, 9 Mar 2006 19:43:13 +0100 Melchior FRANZ wrote: * Curtis L. Olson -- Thursday 09 March 2006 17:59: 2. We need to aggressively hunt down any random crashes I'm aware of four crashes: I've experienced another that I don't think is classifiable in your list. It occurred for me in-flight, during a long flight; but AI traffic wasn't on and I wasn't monitoring ATC. I've been running FG ever since in gdb just in case; but haven't been able to reproduce it. Still trying. In the meantime . . .there's a crash during initialization that I've seen (and posted in this mailing list recently. I'm on an uncommon platform now (AMD64), so I dunno if it's platform dependent, but I wouldn't think so: Chris Metzler wrote: One out of three times I start FlightGear, it immediately crashes back out to the shell prompt with: } FATAL: PUI: No Live Interface! Forgot to call puInit ? I haven't seen anything systematic in either settings or aircraft for which this occurs. It's intermittent, and sometimes repeated tries are necessary to start FG. For example: } stax:~-502 cvsfgfs --aircraft=aerostar-yasim } FATAL: PUI: No Live Interface! Forgot to call puInit ? } } stax:~-503 cvsfgfs --aircraft=aerostar-yasim } FATAL: PUI: No Live Interface! Forgot to call puInit ? } } stax:~-504 cvsfgfs --aircraft=aerostar-yasim } FATAL: PUI: No Live Interface! Forgot to call puInit ? } } stax:~-505 cvsfgfs --aircraft=aerostar-yasim } FATAL: PUI: No Live Interface! Forgot to call puInit ? } } stax:~-506 cvsfgfs --aircraft=aerostar-yasim } Initialising callsign using 'Aircraft/Aerostar-700/Models/aerostar.xml' } Initializing Flight Director } Initializing Nasal Electrical System } Initializing Aircraft Systems [ rest of successful startup and normal execution deleted ] In the list archives, the only previous mention I see of this message is from a year and a half ago, and it wasn't happening on startup. Anyone else see this? Anyone have an idea how to make it stop? -c -- Chris Metzler [EMAIL PROTECTED] (remove snip-me. to email) As a child I understood how to give; I have forgotten this grace since I have become civilized. - Chief Luther Standing Bear signature.asc Description: PGP signature
