On 24 Apr 2012, at 11:41, Renk Thorsten wrote:
> Here's the output:
>
> (gdb) bt
> #0 0x5e3d9a08 in ?? ()
> #1 0x088dd542 in hashForAirport (c=0x13bedd28, apt=0xdcd3988)
> at /home/fgfs/CMake/flightgear/src/Scripting/NasalPositioned.cxx:113
> #2 0x088ddc29 in f_airportinfo (c=0x13bedd28, me=
> {num = nan(0xf678900000000), ref = {ptr = {obj = 0x0, str = 0x0, vec = > 0
> x0, hash = 0x0, code = 0x0, func = 0x0, ccode = 0x0, ghost = 0x0}, reftag =
> 2147
> 444617}}, argc=0, args=0x13bee934)
> at /home/fgfs/CMake/flightgear/src/Scripting/NasalPositioned.cxx:416
> #3 0x08c89a55 in setupFuncall (ctx=0x13bedd28, nargs=0, mcall=0, named=0)
Okay, this is my fault, but I don't know why / how it's crashing for you.
Presumably you have some aircraft or nasal that makes additional airportinfo()
calls, and you've managed to find a test-case that my testing has not
encountered. Unfortunately we need to find out the relevant bit of Nasal I
guess.
I can see it's an airportinfo() call with no arguments, which location are you
at? KSFO right? Hmmmm.
If I launch at KSFO, I get no crash, and I can make airportinfo() calls in the
Nasal console with no problems.
Just to check, you have updated simgear as well? There's a bugfix in there I
applied at the same time.
James
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
