Talk:Building FlightGear - Cross Compiling: Difference between revisions

Jump to navigation Jump to search
Line 213: Line 213:


::: I would suggest running this inside gdb to get an annotated backtrace with source code shown - alternatively, we need to prioritize adding support for BreakPad, which should help with this. Also, is this using the minimal startup profile or just the default settings at ksfo ? If in doubt, I would also check that all sg/fg unit tests are working correctly, to see if that brings up any suspects. But for troubleshooting purposes, I would definitely first try the minimal startup profile as per the article (no multiplayer, scenery, terrasync etc)--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 14:14, 9 June 2015 (EDT)
::: I would suggest running this inside gdb to get an annotated backtrace with source code shown - alternatively, we need to prioritize adding support for BreakPad, which should help with this. Also, is this using the minimal startup profile or just the default settings at ksfo ? If in doubt, I would also check that all sg/fg unit tests are working correctly, to see if that brings up any suspects. But for troubleshooting purposes, I would definitely first try the minimal startup profile as per the article (no multiplayer, scenery, terrasync etc)--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 14:14, 9 June 2015 (EDT)
:::: I'v just read that link you posted about BreakPad, i like the idea of using a crash collecter to store the internal symbols of objects during compilation, so that it can be referenced against a mini-dump. it also support symbols generated in "OS X/Linux, DWARF" format, which is optimal for GCC. should we start to have a central server for crash collection? -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 17:41, 11 June 2015 (EDT)


== OSG static build ==
== OSG static build ==
272

edits

Navigation menu