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
> >
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
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
> > b
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
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
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
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
> &g
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 develope
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 l
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, everythi
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
TrafficManage
No more crash with these files installed.
-Fred
> 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
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 ton
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 f
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:
Using Mac OS X hack for initializing C++ stdio...
Failed to find runway 28R
15 matches
Mail list logo