RE: [Flightgear-devel] MSVC 7.1 Runtime Error

2005-04-29 Thread Ben Morrison
It's not very clear. Check that you added the 
'--fg-root=x:\flightgear\data' parameter to the debugger, not finding 
the airports/runway data can lead FG to an infinite loop for example. Or 
just press break and look where he is in the code ;)

Harald.


Ok, it turns out it was initializing it just wasn't echoing the information
to the command window so I thought it was stuck.  Thanks for your help.

Ben.




___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] MSVC 7.1 Runtime Error

2005-04-29 Thread Harald JOHNSEN
Ben Morrison wrote:
Thanks, guys.  This is my first time posting to the board and I am impressed
with the response times.  I am compiling in debug mode because I am going to
be modifying flightgear later.  Ok, Harald's solution fixed the runtime
error but now flightgear just sits there and doesn't start.  What could be
causing this?
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
 

It's not very clear. Check that you added the 
'--fg-root=x:\flightgear\data' parameter to the debugger, not finding 
the airports/runway data can lead FG to an infinite loop for example. Or 
just press break and look where he is in the code ;)

Harald.

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


RE: [Flightgear-devel] MSVC 7.1 Runtime Error

2005-04-29 Thread Ben Morrison
Thanks, guys.  This is my first time posting to the board and I am impressed
with the response times.  I am compiling in debug mode because I am going to
be modifying flightgear later.  Ok, Harald's solution fixed the runtime
error but now flightgear just sits there and doesn't start.  What could be
causing this?


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] MSVC 7.1 Runtime Error

2005-04-29 Thread Frederic Bouvier
Harald JOHNSEN wrote :
Ben Morrison wrote:
I have downloaded the following source code files: FlightGear 9.8, 
SimGear 3.8, plib 1.8.4, and zlib 1.1.4. I was able to get this to 
compile in Visual Studio 2003 but when I try to run flight gear with 
the following command: “fgfs –fg-root=c:\\GS_PTT\\Flightgear\\data 
–airport=KSFO – aircraft=A-10cl –disable-sound” and I get the 
following runtime error almost immediately:

Debug assertion failed!
Program: fgfs.exe
File: isctype.c
Line: 68
Expression: (unsigned)(c+1) <= 256
Has anyone ever encountered this error? Is it possible to set 
breakpoints in Flightgear and debug it that way?

You can debug, no problem.
The assert is a known problem, it happens with a debug build under VS, 
you have to change a view lines in simgear, patch attached.

BTW: you will get a 2x to 3x framerate improvement if you compile 
flightgear in release mode, and you will not be annoyed by this 
assertion failure.

-Fred

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] MSVC 7.1 Runtime Error

2005-04-29 Thread Harald JOHNSEN
Ben Morrison wrote:
I have downloaded the following source code files: FlightGear 9.8, 
SimGear 3.8, plib 1.8.4, and zlib 1.1.4. I was able to get this to 
compile in Visual Studio 2003 but when I try to run flight gear with 
the following command: “fgfs –fg-root=c:\\GS_PTT\\Flightgear\\data 
–airport=KSFO – aircraft=A-10cl –disable-sound” and I get the 
following runtime error almost immediately:

Debug assertion failed!
Program: fgfs.exe
File: isctype.c
Line: 68
Expression: (unsigned)(c+1) <= 256
Has anyone ever encountered this error? Is it possible to set 
breakpoints in Flightgear and debug it that way?


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
You can debug, no problem.
The assert is a known problem, it happens with a debug build under VS, 
you have to change a view lines in simgear, patch attached.

Harald.
Index: strutils.cxx
===
RCS file: /var/cvs/SimGear-0.3/source/simgear/misc/strutils.cxx,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 strutils.cxx
--- strutils.cxx7 Sep 2002 02:58:19 -   1.1.1.1
+++ strutils.cxx26 Apr 2005 17:01:34 -
@@ -41,14 +41,14 @@
 
while (i < len)
{
-   while (i < len && isspace(str[i]))
+   while (i < len && isspace((unsigned char)str[i]))
{
++i;
}
 
j = i;
 
-   while (i < len && !isspace(str[i]))
+   while (i < len && !isspace((unsigned char)str[i]))
{
++i;
}
@@ -57,7 +57,7 @@
{
result.push_back( str.substr(j, i-j) );
++countsplit;
-   while (i < len && isspace(str[i]))
+   while (i < len && isspace((unsigned char)str[i]))
{
++i;
}

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d