Re: [Flightgear-devel] Latest CVS Aborts

2004-07-23 Thread Durk Talsma
I'll wrap up the new traffic files tonight. I the mean time, I've add small 
tar file containing the necessary traffic files. Should work, but haven't had 
much chance of testing it.

Cheers,
Durk

On Friday 23 July 2004 07:21, Frederic Bouvier wrote:
 Jonathan Polley wrote:
  I just updated tonight and FlightGear no longer runs on the Mac.  As of
  last night, everything ran just file, but after updating everything
  (SimGear, FlightGear, and base packages) I get an abort.  The gdb
  backtrace is:

 ...



traffic-temp.tar.gz
Description: application/tgz
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


Re: [Flightgear-devel] Latest CVS Aborts

2004-07-23 Thread Erik Hofman
Jonathan Polley wrote:
I just updated tonight and FlightGear no longer runs on the Mac.  As of 
last night, everything ran just file, but after updating everything 
(SimGear, FlightGear, and base packages) I get an abort.
Oops, sorry all. This is caused by me not including a bunch of 
TrafficManager related files to the base package.

Although it probably shouldn't trigger a segmentation fault, it is my 
bad and is fixed in CVS now.

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


RE: [Flightgear-devel] Latest CVS Aborts

2004-07-23 Thread Vivian Meazza




Erik Hofman

 Sent: 23 July 2004 08:52
 To: FlightGear developers discussions
 Subject: Re: [Flightgear-devel] Latest CVS Aborts
 
 Jonathan Polley wrote:
  I just updated tonight and FlightGear no longer runs on the Mac.  As of
  last night, everything ran just file, but after updating everything
  (SimGear, FlightGear, and base packages) I get an abort.
 
 Oops, sorry all. This is caused by me not including a bunch of
 TrafficManager related files to the base package.
 
 Although it probably shouldn't trigger a segmentation fault, it is my
 bad and is fixed in CVS now.


As of 1000hrs this morning, it's still broken for Cygwin:

Adding subsystem Traffic Manager
Unknown exception in the main loop. Aborting...

Regards,

Vivian



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


Re: [Flightgear-devel] Latest CVS Aborts

2004-07-23 Thread Frederic Bouvier
Vivian Meazza wrote:
 Erik Hofman
 
  Sent: 23 July 2004 08:52
  To: FlightGear developers discussions
  Subject: Re: [Flightgear-devel] Latest CVS Aborts
  
  Jonathan Polley wrote:
   I just updated tonight and FlightGear no longer runs on the Mac. As of
   last night, everything ran just file, but after updating everything
   (SimGear, FlightGear, and base packages) I get an abort.
  
  Oops, sorry all. This is caused by me not including a bunch of
  TrafficManager related files to the base package.
  
  Although it probably shouldn't trigger a segmentation fault, it is my
  bad and is fixed in CVS now.
 
 
 As of 1000hrs this morning, it's still broken for Cygwin:
 
 Adding subsystem Traffic Manager
 Unknown exception in the main loop. Aborting...

Could you post a gdb backtrace ?

-Fred


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


RE: [Flightgear-devel] Latest CVS Aborts

2004-07-23 Thread Vivian Meazza


Frederic Bouvier asked

 Sent: 23 July 2004 11:14
 To: FlightGear developers discussions
 Subject: Re: [Flightgear-devel] Latest CVS Aborts
 
 Vivian Meazza wrote:
  Erik Hofman
 
   Sent: 23 July 2004 08:52
   To: FlightGear developers discussions
   Subject: Re: [Flightgear-devel] Latest CVS Aborts
  
   Jonathan Polley wrote:
I just updated tonight and FlightGear no longer runs on the Mac. As
 of
last night, everything ran just file, but after updating everything
(SimGear, FlightGear, and base packages) I get an abort.
  
   Oops, sorry all. This is caused by me not including a bunch of
   TrafficManager related files to the base package.
  
   Although it probably shouldn't trigger a segmentation fault, it is my
   bad and is fixed in CVS now.
 
 
  As of 1000hrs this morning, it's still broken for Cygwin:
 
  Adding subsystem Traffic Manager
  Unknown exception in the main loop. Aborting...
 
 Could you post a gdb backtrace ?
 

Br, I've just reverted to 0.9.5-pre1. Standby.

Regards,

Vivian




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


RE: [Flightgear-devel] Latest CVS Aborts

2004-07-23 Thread Vivian Meazza



 I wrote

 Sent: 23 July 2004 11:49
 To: 'FlightGear developers discussions'
 Subject: RE: [Flightgear-devel] Latest CVS Aborts
 
 
 
 Frederic Bouvier asked
 
  Sent: 23 July 2004 11:14
  To: FlightGear developers discussions
  Subject: Re: [Flightgear-devel] Latest CVS Aborts
 
  Vivian Meazza wrote:
   Erik Hofman
  
Sent: 23 July 2004 08:52
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Latest CVS Aborts
   
Jonathan Polley wrote:
 I just updated tonight and FlightGear no longer runs on the Mac.
 As
  of
 last night, everything ran just file, but after updating
 everything
 (SimGear, FlightGear, and base packages) I get an abort.
   
Oops, sorry all. This is caused by me not including a bunch of
TrafficManager related files to the base package.
   
Although it probably shouldn't trigger a segmentation fault, it is
 my
bad and is fixed in CVS now.
  
  
   As of 1000hrs this morning, it's still broken for Cygwin:
  
   Adding subsystem Traffic Manager
   Unknown exception in the main loop. Aborting...
 
  Could you post a gdb backtrace ?
 
 
 Br, I've just reverted to 0.9.5-pre1. Standby.
 

I've re-downloaded the current cvs. Here's the backtrace

(gdb) backtrace
#0  0x77e75a3f in KERNEL32!IsBadWritePtr ()
   from /cygdrive/c/WINDOWS/system32/kernel32.dll
#1  0x0013 in ?? ()
#2  0x0022d634 in ?? ()
#3  0x0012 in ?? ()
#4  0x0022d000 in ?? ()
#5  0x0022d000 in ?? ()
#6  0x0022bfec in ?? ()
#7  0x63656a62 in ?? ()
#8  0x0022f090 in ?? ()
#9  0x77e94809 in SetThreadExecutionState ()
   from /cygdrive/c/WINDOWS/system32/kernel32.dll
#10 0x610a92ed in cygwin1!__getreent () from /usr/bin/cygwin1.dll
#11 0x0008 in ?? ()
#12 0x0022c048 in ?? ()
#13 0x610a9387 in cygwin1!__getreent () from /usr/bin/cygwin1.dll
#14 0x0001 in ?? ()
#15 0x0022c120 in ?? ()
#16 0x0022d634 in ?? ()
(gdb)

Can't say that it means anything to me! Is it any good to you, or can I do
something else?

Regards,

Vivian



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


Re: [Flightgear-devel] Latest CVS Aborts

2004-07-23 Thread Frederic Bouvier
Vivian Meazza wrote:
 I've re-downloaded the current cvs. Here's the backtrace
...
 
 Can't say that it means anything to me! Is it any good to you, or can I do
 something else?

It looks like useless garbage, sorry. Do you run fg with --log-level=bulk 
or whatever is the most verbose ( I don't remember right now ) ?

-Fred


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


Re: [Flightgear-devel] Latest CVS Aborts

2004-07-23 Thread Curtis L. Olson
Frederic Bouvier wrote:
Vivian Meazza wrote:
 

I've re-downloaded the current cvs. Here's the backtrace
   

...
 

Can't say that it means anything to me! Is it any good to you, or can I do
something else?
   

It looks like useless garbage, sorry. Do you run fg with --log-level=bulk 
or whatever is the most verbose ( I don't remember right now ) ?
 

You have to compile with -g to include debugging symbols so that the 
back trace makes sense.  That said, the very few times I've tried to run 
gdb with flightgear on windows, I was never very successful.

Curt.
--
Curtis Olsonhttp://www.flightgear.org/~curt 
HumanFIRST Program  http://www.humanfirst.umn.edu/
FlightGear Project  http://www.flightgear.org
Unique text:2f585eeea02e2c79d7b1d8c4963bae2d

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


RE: [Flightgear-devel] Latest CVS Aborts

2004-07-23 Thread Norman Vine
Curtis L. Olson writes:
 
 You have to compile with -g to include debugging symbols so that the 
 back trace makes sense.  That said, the very few times I've tried to run 
 gdb with flightgear on windows, I was never very successful.

GDB might have some problems on 95,98 and WinMe,  but runs fine 
on any WindowsNT variant.

Of course as Curt says you do need to compile with the -g switch
for debugging I usually use  'CXXFLAGS = -g -O2'
which IIRC is the default setting for our configure scripts

Norman

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


RE: [Flightgear-devel] Latest CVS Aborts

2004-07-23 Thread Vivian Meazza

Norman Vine wrote

 Sent: 23 July 2004 14:15
 To: FlightGear developers discussions
 Subject: RE: [Flightgear-devel] Latest CVS Aborts
 
 Curtis L. Olson writes:
 
  You have to compile with -g to include debugging symbols so that the
  back trace makes sense.  That said, the very few times I've tried to run
  gdb with flightgear on windows, I was never very successful.
 
 GDB might have some problems on 95,98 and WinMe,  but runs fine
 on any WindowsNT variant.
 
 Of course as Curt says you do need to compile with the -g switch
 for debugging I usually use  'CXXFLAGS = -g -O2'
 which IIRC is the default setting for our configure scripts
 
 Norman

I'd forgotten the -g. I'll re-download, recompile and try again.

Regards,

Vivian




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


RE: [Flightgear-devel] Latest CVS Aborts

2004-07-23 Thread Vivian Meazza

Frederic Bouvier asked

 Sent: 23 July 2004 13:51
 To: FlightGear developers discussions
 Subject: Re: [Flightgear-devel] Latest CVS Aborts
 
 Vivian Meazza wrote:
  I've re-downloaded the current cvs. Here's the backtrace
 ...
 
  Can't say that it means anything to me! Is it any good to you, or can I
 do
  something else?
 
 It looks like useless garbage, sorry. Do you run fg with --log-level=bulk
 or whatever is the most verbose ( I don't remember right now ) ?

--log-level=info - second most verbose

Regards,

Vivian



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


RE: [Flightgear-devel] Latest CVS Aborts

2004-07-23 Thread Vivian Meazza


I wrote

 Sent: 23 July 2004 14:39
 To: 'FlightGear developers discussions'
 Subject: RE: [Flightgear-devel] Latest CVS Aborts
 
 
 Frederic Bouvier asked
 
  Sent: 23 July 2004 13:51
  To: FlightGear developers discussions
  Subject: Re: [Flightgear-devel] Latest CVS Aborts
 
  Vivian Meazza wrote:
   I've re-downloaded the current cvs. Here's the backtrace
  ...
  
   Can't say that it means anything to me! Is it any good to you, or can
 I
  do
   something else?
 
  It looks like useless garbage, sorry. Do you run fg with --log-
 level=bulk
  or whatever is the most verbose ( I don't remember right now ) ?
 
 --log-level=info - second most verbose
 

Latest cvs download compiled successfully under Cygwin, by the usual
expedient of deleting all old files and starting over. Tedious, but it
worked. I have no idea what was wrong, but it looks like a file wasn't being
updated by cvs correctly.

Once again thanks for your help

Regards,

Vivian



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


Re: [Flightgear-devel] Latest CVS Aborts

2004-07-22 Thread Frederic Bouvier
Jonathan Polley wrote:

 I just updated tonight and FlightGear no longer runs on the Mac.  As of
 last night, everything ran just file, but after updating everything
 (SimGear, FlightGear, and base packages) I get an abort.  The gdb
 backtrace is:

...

It is the same for everybody until some files required by the TrafficManager
are put in CVS.

-Fred



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