Re: [Flightgear-devel] Latest CVS Crashes

2002-11-12 Thread Curtis L. Olson
Just to double check, David made a change to SimGear and to the some
of the aircraft config files yesterday.  Without the change to
simgear, flightgear will crash on startup.

If that's not it, then we'll have to take a closer look, although your
line numbers don't make sense in your back trace ...

Regards,

Curt.


Jonathan Polley writes:
 I just updated from CVS for both the Mac and Windows and got the same 
 error when I tried to run.  The Mac traceback is as follows:
 
 
 
 Exception:  EXC_BAD_ACCESS (0x0001)
 Codes:  KERN_PROTECTION_FAILURE (0x0002) at 0x0006
 
 Thread 0 Crashed:
   #0   0x000525f8 in ssgContext::forceBasicState() (ssgContext.cxx:103)
   #1   0x00038464 in ssgCullAndDraw(ssgBranch*) (ssg.cxx:273)
   #2   0x427c in fgRenderFrame() (main.cxx:2143)
   #3   0x6284 in fgMainLoop() (main.cxx:271)
   #4   0x90163888 in __CFRunLoopDoTimer
   #5   0x901493e0 in __CFRunLoopRun
   #6   0x9018157c in CFRunLoopRunSpecific
   #7   0x92ba34cc in RunCurrentEventLoopInMode
   #8   0x92bb32f4 in ReceiveNextEventCommon
   #9   0x92bda280 in BlockUntilNextEventMatchingListInMode
   #10  0x93082184 in _DPSNextEvent
   #11  0x930ccf84 in -[NSApplication 
 nextEventMatchingMask:untilDate:inMode:dequeue:]
   #12  0x930ca500 in -[NSApplication run]
   #13  0x94fd9110 in glutMainLoop
   #14  0x8c7c in mainLoop(int, char**) (main.cxx:1746)
   #15  0x8dd4 in main (main.cxx:1834)
   #16  0x2b5c in _start (crt.c:267)
   #17  0x29dc in start
 
 
 The error was in the same routine, so I am assuming that there is 
 something uninitialized somewhere.  The bad pointer was in slightly 
 different lines of code, though:
 
if ( ovState != NULL )
  ovState - force () ;   --- Windows Crashes
else
  basicState - force () ;  --- Mac Crashes
 
 Windows died where it did because ovState contained the Windows 
 non-zero invalid pointer value (0xcacacaca).
 
 Jonathan Polley
 
 
 ___
 Flightgear-devel mailing list
 [EMAIL PROTECTED]
 http://mail.flightgear.org/mailman/listinfo/flightgear-devel

-- 
Curtis Olson   IVLab / HumanFIRST Program   FlightGear Project
Twin Cities[EMAIL PROTECTED]  [EMAIL PROTECTED]
Minnesota  http://www.menet.umn.edu/~curt   http://www.flightgear.org

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] Latest CVS Crashes

2002-11-12 Thread Jonathan Polley
Curt,

	I updated plib, SimGear, and FlightGear before rebuilding.  I cleaned 
everything on Windows because there were some changes to plib headers 
(MSVC isn't always smart enough to properly handle header changes if 
they are not in YOUR project).  I haven't cleaned the MacOS build 
because gcc hasn't had such problems.

Jonathan Polley

On Tuesday, November 12, 2002, at 06:43  AM, Curtis L. Olson wrote:

Just to double check, David made a change to SimGear and to the some
of the aircraft config files yesterday.  Without the change to
simgear, flightgear will crash on startup.

If that's not it, then we'll have to take a closer look, although your
line numbers don't make sense in your back trace ...

Regards,

Curt.


Jonathan Polley writes:

I just updated from CVS for both the Mac and Windows and got the same
error when I tried to run.  The Mac traceback is as follows:



Exception:  EXC_BAD_ACCESS (0x0001)
Codes:  KERN_PROTECTION_FAILURE (0x0002) at 0x0006

Thread 0 Crashed:
  #0   0x000525f8 in ssgContext::forceBasicState() 
(ssgContext.cxx:103)
  #1   0x00038464 in ssgCullAndDraw(ssgBranch*) (ssg.cxx:273)
  #2   0x427c in fgRenderFrame() (main.cxx:2143)
  #3   0x6284 in fgMainLoop() (main.cxx:271)
  #4   0x90163888 in __CFRunLoopDoTimer
  #5   0x901493e0 in __CFRunLoopRun
  #6   0x9018157c in CFRunLoopRunSpecific
  #7   0x92ba34cc in RunCurrentEventLoopInMode
  #8   0x92bb32f4 in ReceiveNextEventCommon
  #9   0x92bda280 in BlockUntilNextEventMatchingListInMode
  #10  0x93082184 in _DPSNextEvent
  #11  0x930ccf84 in -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:]
  #12  0x930ca500 in -[NSApplication run]
  #13  0x94fd9110 in glutMainLoop
  #14  0x8c7c in mainLoop(int, char**) (main.cxx:1746)
  #15  0x8dd4 in main (main.cxx:1834)
  #16  0x2b5c in _start (crt.c:267)
  #17  0x29dc in start


The error was in the same routine, so I am assuming that there is
something uninitialized somewhere.  The bad pointer was in slightly
different lines of code, though:

   if ( ovState != NULL )
 ovState - force () ;   --- Windows Crashes
   else
 basicState - force () ;  --- Mac Crashes

Windows died where it did because ovState contained the Windows
non-zero invalid pointer value (0xcacacaca).

Jonathan Polley


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

--
Curtis Olson   IVLab / HumanFIRST Program   FlightGear Project
Twin Cities[EMAIL PROTECTED]  [EMAIL PROTECTED]
Minnesota  http://www.menet.umn.edu/~curt   
http://www.flightgear.org

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] Latest CVS Crashes

2002-11-12 Thread David Megginson
Jonathan Polley writes:

   I updated plib, SimGear, and FlightGear before rebuilding.  I cleaned 
  everything on Windows because there were some changes to plib headers 
  (MSVC isn't always smart enough to properly handle header changes if 
  they are not in YOUR project).  I haven't cleaned the MacOS build 
  because gcc hasn't had such problems.

You have to make sure that FlightGear rebuilds.  When there's a
SimGear change that doesn't touch any headers, FlightGear might not
automatically rebuild -- you have to delete the fgfs (or fgfs.exe)
binary and then do a make.


All the best,


David

-- 
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] Latest CVS Crashes

2002-11-12 Thread Andy Ross
Jonathan Polley wrote:
 I updated plib, SimGear, and FlightGear before rebuilding.  I cleaned
 everything on Windows because there were some changes to plib headers
 (MSVC isn't always smart enough to properly handle header changes if
 they are not in YOUR project).  I haven't cleaned the MacOS build
 because gcc hasn't had such problems.

I just got bitten by this too after a CVS update.  Your diagnosis was
correct; it's a plib bug.  Changes that Steve made two days ago
introduced an new variable without a default initialization.  Here's
the note I just sent to the plib list:

 The most recent changes have an uninitialized data bug.  The new
 ssgContext member ovState is never assigned to a default value in
 the constructor, but is nonetheless tested against NULL at runtime.
 Trivial patch follows.

 Andy

 diff -u -r1.19 ssgContext.cxx
 --- ssgContext.cxx  10 Nov 2002 17:12:13 -  1.19
 +++ ssgContext.cxx  12 Nov 2002 21:14:07 -
 @@ -48,6 +48,7 @@
cullFace = TRUE  ;
ovTexture= FALSE ;
ovCullface   = FALSE ;
 +  ovState  = NULL  ;

sgCopyMat4 ( cameraMatrix, _ssgOpenGLAxisSwapMatrix ) ;

Andy

--
Andrew J. RossNextBus Information Systems
Senior Software Engineer  Emeryville, CA
[EMAIL PROTECTED]  http://www.nextbus.com
Men go crazy in conflagrations.  They only get better one by one.
 - Sting (misquoted)


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] Latest CVS Crashes

2002-11-12 Thread Jonathan Polley
Andy,

	That fixed the problem.  Thanks!

Jonathan Polley

On Tuesday, November 12, 2002, at 03:21  PM, Andy Ross wrote:


Jonathan Polley wrote:
 I updated plib, SimGear, and FlightGear before rebuilding.  I cleaned
 everything on Windows because there were some changes to plib headers
 (MSVC isn't always smart enough to properly handle header changes if
 they are not in YOUR project).  I haven't cleaned the MacOS build
 because gcc hasn't had such problems.

I just got bitten by this too after a CVS update.  Your diagnosis was
correct; it's a plib bug.  Changes that Steve made two days ago
introduced an new variable without a default initialization.  Here's
the note I just sent to the plib list:

 The most recent changes have an uninitialized data bug.  The new
 ssgContext member ovState is never assigned to a default value in
 the constructor, but is nonetheless tested against NULL at runtime.
 Trivial patch follows.

 Andy

 diff -u -r1.19 ssgContext.cxx
 --- ssgContext.cxx  10 Nov 2002 17:12:13 -  1.19
 +++ ssgContext.cxx  12 Nov 2002 21:14:07 -
 @@ -48,6 +48,7 @@
cullFace = TRUE  ;
ovTexture= FALSE ;
ovCullface   = FALSE ;
 +  ovState  = NULL  ;

sgCopyMat4 ( cameraMatrix, _ssgOpenGLAxisSwapMatrix ) ;

Andy

--
Andrew J. RossNextBus Information Systems
Senior Software Engineer  Emeryville, CA
[EMAIL PROTECTED]  http://www.nextbus.com
Men go crazy in conflagrations.  They only get better one by one.
 - Sting (misquoted)


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



[Flightgear-devel] Latest CVS Crashes

2002-11-11 Thread Jonathan Polley
I just updated from CVS for both the Mac and Windows and got the same 
error when I tried to run.  The Mac traceback is as follows:



Exception:  EXC_BAD_ACCESS (0x0001)
Codes:  KERN_PROTECTION_FAILURE (0x0002) at 0x0006

Thread 0 Crashed:
 #0   0x000525f8 in ssgContext::forceBasicState() (ssgContext.cxx:103)
 #1   0x00038464 in ssgCullAndDraw(ssgBranch*) (ssg.cxx:273)
 #2   0x427c in fgRenderFrame() (main.cxx:2143)
 #3   0x6284 in fgMainLoop() (main.cxx:271)
 #4   0x90163888 in __CFRunLoopDoTimer
 #5   0x901493e0 in __CFRunLoopRun
 #6   0x9018157c in CFRunLoopRunSpecific
 #7   0x92ba34cc in RunCurrentEventLoopInMode
 #8   0x92bb32f4 in ReceiveNextEventCommon
 #9   0x92bda280 in BlockUntilNextEventMatchingListInMode
 #10  0x93082184 in _DPSNextEvent
 #11  0x930ccf84 in -[NSApplication 
nextEventMatchingMask:untilDate:inMode:dequeue:]
 #12  0x930ca500 in -[NSApplication run]
 #13  0x94fd9110 in glutMainLoop
 #14  0x8c7c in mainLoop(int, char**) (main.cxx:1746)
 #15  0x8dd4 in main (main.cxx:1834)
 #16  0x2b5c in _start (crt.c:267)
 #17  0x29dc in start


The error was in the same routine, so I am assuming that there is 
something uninitialized somewhere.  The bad pointer was in slightly 
different lines of code, though:

  if ( ovState != NULL )
ovState - force () ;   --- Windows Crashes
  else
basicState - force () ;  --- Mac Crashes

Windows died where it did because ovState contained the Windows 
non-zero invalid pointer value (0xcacacaca).

Jonathan Polley


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel