Talk:Building FlightGear - Cross Compiling: Difference between revisions

Jump to navigation Jump to search
m
→‎Simgear Test Crashes: http://sourceforge.net/p/flightgear/simgear/ci/next/tree/simgear/nasal/cppbind/test/
m (→‎Simgear Test Crashes: http://sourceforge.net/p/flightgear/simgear/ci/next/tree/simgear/nasal/cppbind/test/)
Line 260: Line 260:


: It's definitely something in Simgear's ghost (or in calling ghost). I've built a 64-bit shared version of Flightgear, and it crashes when calling nasal::internal::GhostMetadata::addDerived. GDB backtrace is [https://gist.github.com/saiarcot895/0d795876ad3913023514 here] -- [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 11:05, 24 June 2015 (EDT)
: It's definitely something in Simgear's ghost (or in calling ghost). I've built a 64-bit shared version of Flightgear, and it crashes when calling nasal::internal::GhostMetadata::addDerived. GDB backtrace is [https://gist.github.com/saiarcot895/0d795876ad3913023514 here] -- [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 11:05, 24 June 2015 (EDT)
:: That's [[Nasal/CppBind]] (Nasal related code using boost) - can you check if the Nasal unit tests are working correctly or not ? Also, what about Nasal standalone (no boost there). Alternatively, use boost to print out some more info: http://www.boost.org/doc/libs/1_55_0/libs/test/doc/html/utf/user-guide/runtime-config/reference.html Basically, I would suggest to eliminate fgfs to get down to this, some of the unit tests should be sufficiently self-contained to troubleshoot this: http://sourceforge.net/p/flightgear/simgear/ci/next/tree/simgear/nasal/cppbind/test/ --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 11:20, 24 June 2015 (EDT)


== Breakpad.mk ==
== Breakpad.mk ==

Navigation menu