Hi Jari, Thanks for the log.
On Jan 10, 2010, at 5:32 AM, Jari Häkkinen wrote: > On 2010-01-06 05.51, Tatsuhiro Nishioka wrote: >> To get the GUI side log more precisely, could you run the GUI from >> terminal using the commands below?: >> >> cd /Applications/FlightGear.app/Contents/MacOS >> ./FlightGear > > The output to the terminal is attached as file fg_mac2pre1.log. As indicated > in the log file I deleted many repeated lines. > > The two first lines are produced when the launcher is started and the rest is > created when I click on the 'Start Flight' button. The crash is caused by one line on the Ruby code that pulls a RubyCocoa bug. I fixed the problem on the GUI side, and packed it into GUI updater with other bug-fixes and new Atlas. The updater is available at: http://macflightgear.sourceforge.net/wp-content/uploads/launcher/2.0.0-pre1/GUIUpdater-2.0.0-pre1-r273.tgz The updater fixes: - Some wrong runway data on GUI - Crashes when pressing a gear icon - Crashes when pressing "Start Flight" button (probably on Snow Leopard) - terrasync didn't work on Tiger properly - Aircraft preview crashes - Some terms were not translated on GUI components - Missing carriers on airport list. - Missing Gear Icon on Tiger The latest Atlas/CVS was built on 12/28 IIRC. > >> These will give you all launcher related logs on the terminal. Fgfs >> log will be stored at ~/.fgfs/log.txt > > The log.txt contains four lines > > GraphicsWindowCarbon::grabFocusIfPointerInWindow > Failed to load file: "Aircraft/c172p/Models/Pedals/pedals.xml" > Failed to load file: "Aircraft/c172p/Models/Pedals/pedals.xml" > Unknown exception in the main loop. Aborting... > > >> The crash on iMac needs to be investigated more. You can go to the >> Resources folder and run fgfs.sh with options of your choice. This >> will isolate the problems of fgfs from the GUI launcher part. > > Trying to start fg with fgfs.sh simply presents the splash screen for a few > seconds and dies. The log file content is the same as above, nothing is > written to the terminal. Could you increase the log level? Trying --log-level=info option on fgfs will tell you more info. If this doesn't help you find a problem, please try: OSG_NOTIFY_LEVEL=info ./fgfs.sh or OSG_NOTIFY_LEVEL=debug ./fgfs.sh > >> However, it's good to hear that the fgfs/cvs-head works on iMac. It's >> newer than pre-1 code. >> >> Btw are you using what version of OSG? > > I am using the latest version from the OSG subversion repository. It is now > 2.9.7+ Oh, no crash on static_initialization? I've got the crash on osgFX every time I build FG with OSG/svn-head (or 2.9.6) since some time around Dec. 01. This crash happens with both g++-4.0.1 and g++-4.2 I guess this is due to a g++ bug that is fixed after 4.2 since you don't get it crashed. This is why I need to use OSG-2.9.5 with my patches applied to OSG-2.9.6 Best, Tat ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Flightgear-users mailing list Flightgear-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-users
