[Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.
Now when it comes to debugging stuff like this I'm a newbie.When I select the default c172p aircraft everything works fine. But if I select say the f16 or A-10 then fgfs crashes.Here's the output from gdb. Loading program into debugger… Program loaded.sharedlibrary apply-load-rules all Attaching to program: `/Users/arthur/Projects/FlightGearOSX/build/FlightGear/FlightGear.app/Contents/MacOS/FlightGear', process 5516. mi_cmd_stack_list_frames: Not enough frames in stack.mi_cmd_stack_list_frames: Not enough frames in stack. I never tested pre1 or pre2 with different aircraft so don't know if I got the error then too.-- Arthur/- http://sourceforge.net/users/artooro/ - http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.
Arthur Wiebe wrote: Now when it comes to debugging stuff like this I'm a newbie. When I select the default c172p aircraft everything works fine. But if I select say the f16 or A-10 then fgfs crashes. Here's the output from gdb. http://www.codecomments.com/archive242-2004-4-170396.html The problem is gdb. It is the debugger itself that cause the error when stepping instruction. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.
OK,But then why when I select the A-10 or f16 fgfs crashes? But when selecting the c172p and j3cub there is no problem?I'll do a bit more testing.It almost seems to be a problem with the actual aircraft. On 11/11/05, Erik Hofman [EMAIL PROTECTED] wrote: Arthur Wiebe wrote: Now when it comes to debugging stuff like this I'm a newbie. When I select the default c172p aircraft everything works fine. But if I select say the f16 or A-10 then fgfs crashes. Here's the output from gdb.http://www.codecomments.com/archive242-2004-4-170396.html The problem is gdb. It is the debugger itself that cause the error when stepping instruction.Erik___Flightgear-devel mailing list Flightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel2f585eeea02e2c79d7b1d8c4963bae2d -- Arthur/- http://sourceforge.net/users/artooro/- http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.
Arthur Wiebe wrote: OK, But then why when I select the A-10 or f16 fgfs crashes? But when selecting the c172p and j3cub there is no problem? The only commonality between the A-10 and f-16 is the turbine sound file?? Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.
I've compiled a list of all the aircraft included in fgfs-base 0.9.9pre3 that do and don't work:+737-.#A-10cl-A-10cl-A-10fl+bo105+c172p-2dpanel+c172p+c310-yasim+c310dpm-3d-c310-3d +c310-ifr+c310+c310u3a-jsbsim+c310u3a+Citation-||-f16-3d-f16-mlu-f16-f16at+hunter-2tanks+hunter+j3cub+p51d+pa28-161+ufo+wrightFlyer1903Those with a + work and those with the - do not. I wonder what .#A-10cl is doing in there as it's invisible for most people.On 11/11/05, Erik Hofman [EMAIL PROTECTED] wrote:Arthur Wiebe wrote: OK, But then why when I select the A-10 or f16 fgfs crashes? But when selecting the c172p and j3cub there is no problem?The only commonality between the A-10 and f-16 is the turbine sound file??Erik___Flightgear-devel mailing list Flightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d-- Arthur/- http://sourceforge.net/users/artooro/- http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.
OK I found the problem. I hope.In A-10cl-set.xml I removed the following line: splash-textureAircraft/A-10/A-10-splash.rgb/splash-textureAnd it worked. So it seems something is broken in whatever loads these rgb files. The file does not look corrupted as it opens fine in QuickTime.On 11/11/05, Arthur Wiebe [EMAIL PROTECTED] wrote:I've compiled a list of all the aircraft included in fgfs-base 0.9.9pre3 that do and don't work: +737-.#A-10cl-A-10cl-A-10fl+bo105+c172p-2dpanel+c172p+c310-yasim+c310dpm-3d-c310-3d +c310-ifr+c310+c310u3a-jsbsim+c310u3a+Citation-||-f16-3d-f16-mlu-f16-f16at+hunter-2tanks+hunter+j3cub+p51d+pa28-161+ufo+wrightFlyer1903Those with a + work and those with the - do not. I wonder what .#A-10cl is doing in there as it's invisible for most people.On 11/11/05, Erik Hofman [EMAIL PROTECTED] wrote:Arthur Wiebe wrote: OK, But then why when I select the A-10 or f16 fgfs crashes? But when selecting the c172p and j3cub there is no problem?The only commonality between the A-10 and f-16 is the turbine sound file??Erik___Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d-- Arthur/- http://sourceforge.net/users/artooro/- http://artooro.blogspot.com -- Arthur/- http://sourceforge.net/users/artooro/- http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.
On Friday 11 Nov 2005 17:35, Erik Hofman wrote: Arthur Wiebe wrote: OK, But then why when I select the A-10 or f16 fgfs crashes? But when selecting the c172p and j3cub there is no problem? The only commonality between the A-10 and f-16 is the turbine sound file?? Erik Agreed - I used the generic sound files for the A-10 but the engine related ones are probably the only ones common to the F-16 and A-10 but not used by the C-172 or j3 cub. LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
