Re: [Jsbsim-devel] Using FlightGear to visualize JSBSim state

[D W. <hdw...@gm...>]

>  By 'unhelpful win32 message' I meant the informative JIT debugger msg 'An
> unhandled win32 exception occured in JSBSim.exe [3744].' if you don't have
> VS then you simply get the option to send Microsoft an error report. (Maybe
> they'll fix it?)

Ugggh.  I was hoping the message would be less "unhelpful" than that.

BTW, I just ran the latest version of JSBSim pulled from CVS here and
all is still well (Linux 2.6.22 and FG 0.9.11-pre1 for visuals).

>  JSBSim socket related messages are:
>  Winsock DLL loaded ...
>  Creating TCP socket on port 5500
>  Successfully connected to socket for output ...
>   Output parameters read inline

The socket init seems to be valid.  If you kick off JSBSim without the
remote FG running do you see a stream of "send:  Connection refused"
messages?

>  Here's the last few lines of output from the VC++ output window:
>
>  ... 'JSBSim.exe': Loaded 'C:\WINDOWS\SysWOW64\setupapi.dll', No symbols
> loaded. First-chance exception at 0x7d4e2366 in JSBSim.exe: 0x000006C5: The
> tag is invalid. 'JSBSim.exe': Loaded 'C:\WINDOWS\SysWOW64\rasadhlp.dll', No
> symbols loaded. 'JSBSim.exe': Loaded 'C:\WINDOWS\SysWOW64\hnetcfg.dll', No
> symbols loaded. 'JSBSim.exe': Loaded 'C:\WINDOWS\SysWOW64\wshtcpip.dll', No
> symbols loaded. The thread 'Win32 Thread' (0x6e8) has exited with code 0
> (0x0). The program '[1888] JSBSim.exe: Native' has exited with code -1
> (0xffffffff).
>
>  Note that I am compiling this on a 64bit OS, I have not had the chance to
> compile it on a 32bit one yet. I also have not yet found the exact part of
> the code where the exception is thrown in the debugger.

All of that DLL stuff looks like jibber-jabber to me.  "SysWOW64" made
me laugh, though.  "Wow!" is right.  ;-)

Perhaps it's worth trying to compile a simple client/server example on
your 64b system to see if it tanks?  I have an example for Linux if
you want to try to port it.

>  As for the net_fdm header change: Some time ago JSBSim refused to compile
> with VC++ because uint32 and int32 were not defined in net_fdm.hxx. To fix
> this the following typedefs were added:
>
>  #ifdef _MSC_VER   typedef unsigned long uint32_t;   typedef long int32_t;
> #endif
>  (Shouldn't those be long ints? I tried changing them but it doesn't make a
> difference)

Thanks for the heads up.  Minor change which is what I was hoping for.
 Knocking the 'int' off of 'unsigned long' and 'long' in the typedef
won't hurt anything as long as 'long' is still 4 bytes long.

>  I am going to try and compile JSBSim with some other compiler and see if
> this error persists.

Sounds like a good plan.  Please report back.

D