Hi all,
the new METAR handler uses the following code
static const string coverage_string[] = {
SGCloudLayer::SG_CLOUD_CLEAR_STRING,
SGCloudLayer::SG_CLOUD_FEW_STRING,
SGCloudLayer::SG_CLOUD_SCATTERED_STRING,
SGCloudLayer::SG_CLOUD_BROKEN_STRING,
SGCloudLayer::SG_CLOUD_OVERCAST_STRING,
};
which runs fine for me under Linux but crashes my Mac (Windows not yet
tested)
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0xfffffffffffffff8
0x00007fff80ed20aa in std::string::_Rep::_M_grab ()
(gdb) bt
#0 0x00007fff80ed20aa in std::string::_Rep::_M_grab ()
#1 0x00007fff80ed2171 in std::basic_string<char,
std::char_traits<char>, std::allocator<char> >::basic_string ()
#2 0x000000010001ff71 in __static_initialization_and_destruction_0
(__initialize_p=<value temporarily unavailable, due to optimizations>,
__priority=<value temporarily unavailable, due to optimizations>) at
metarproperties.cxx:105
#3 0x00007fff5fc0d500 in
__dyld__ZN16ImageLoaderMachO18doModInitFunctionsERKN11ImageLoader11LinkContextE
()
#4 0x00007fff5fc0bcec in
__dyld__ZN11ImageLoader23recursiveInitializationERKNS_11LinkContextEj ()
#5 0x00007fff5fc0bda6 in
__dyld__ZN11ImageLoader15runInitializersERKNS_11LinkContextE ()
#6 0x00007fff5fc0210e in __dyld__ZN4dyld24initializeMainExecutableEv ()
#7 0x00007fff5fc06981 in
__dyld__ZN4dyld5_mainEPK12macho_headermiPPKcS5_S5_ ()
#8 0x00007fff5fc016d2 in
__dyld__ZN13dyldbootstrap5startEPK12macho_headeriPPKcl ()
#9 0x00007fff5fc01052 in __dyld__dyld_start ()
Does anybody else see this? Is a static string array a bad idea?
Torsten
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
