Re: [Flightgear-devel] another segfault, ATC.hxx

2004-03-01 Thread Jorge Van Hemelryck
On Mon, 1 Mar 2004 21:11:59 + David Luff wrote: > I generated them from the DAFIF data, you (and others) can send > corrections, additions and clarifications to me and I'll store them > and apply them each time the files are regenerated. So far I've only > generated tower and ATIS frequencies

Re: [Flightgear-devel] another segfault, ATC.hxx

2004-03-01 Thread David Luff
Jorge Van Hemelryck writes: > On Mon, 01 Mar 2004 13:55:43 + > David Luff wrote: > > > This should now be fixed. The cause of the problem was that LFMI and LFMY > > have a common tower frequency (122.1), but the commlist code was returning > > the first in-range match rather the closest matc

Re: [Flightgear-devel] another segfault, ATC.hxx

2004-03-01 Thread Jorge Van Hemelryck
On Mon, 01 Mar 2004 13:55:43 + David Luff wrote: > This should now be fixed. The cause of the problem was that LFMI and LFMY > have a common tower frequency (122.1), but the commlist code was returning > the first in-range match rather the closest match when initialising the > tower, resultin

Re: [Flightgear-devel] another segfault, ATC.hxx

2004-03-01 Thread David Luff
On 2/28/04 at 5:50 PM Jorge Van Hemelryck wrote: >Default : 120.5/118.85, 118.3/133.77, but I was at LFMI, not KSFO... I >did have a message saying > >ERROR - can't get a tower pointer from tower control for LFMY in >FGAILocalTraffic::GetAirportDetails() :-( > >just before the segfault, but I ha

Re: [Flightgear-devel] another segfault, ATC.hxx

2004-02-28 Thread Jorge Van Hemelryck
On Sat, 28 Feb 2004 14:34:00 + David Luff wrote: > Thanks for the backtrace, I'll look into it. Do you have any > recollection of what frequencies your comm radios were tuned into at > the time? Default : 120.5/118.85, 118.3/133.77, but I was at LFMI, not KSFO... I did have a message saying

Re: [Flightgear-devel] another segfault, ATC.hxx

2004-02-28 Thread David Luff
Lee Elliott writes: > On Saturday 28 February 2004 15:03, Jorge Van Hemelryck wrote: > > After running fgfs a little while (2-3 minutes)... > > > > $ fgfs > > ERROR - can't get a tower pointer from tower control for LFMY in > > FGAILocalTraffic::GetAirportDetails() :-( Segmentation fault (core dum

Re: [Flightgear-devel] another segfault, ATC.hxx

2004-02-28 Thread Lee Elliott
On Saturday 28 February 2004 15:03, Jorge Van Hemelryck wrote: > After running fgfs a little while (2-3 minutes)... > > $ fgfs > ERROR - can't get a tower pointer from tower control for LFMY in > FGAILocalTraffic::GetAirportDetails() :-( Segmentation fault (core dumped) I've been getting quite a f

Re: [Flightgear-devel] another segfault, ATC.hxx

2004-02-28 Thread David Luff
Jorge Van Hemelryck writes: > After running fgfs a little while (2-3 minutes)... > > $ fgfs > ERROR - can't get a tower pointer from tower control for LFMY in > FGAILocalTraffic::GetAirportDetails() :-( > Segmentation fault (core dumped) > $ gdb fgfs > (...) > Core was generated by `fgfs'. > Pro

[Flightgear-devel] another segfault, ATC.hxx

2004-02-28 Thread Jorge Van Hemelryck
After running fgfs a little while (2-3 minutes)... $ fgfs ERROR - can't get a tower pointer from tower control for LFMY in FGAILocalTraffic::GetAirportDetails() :-( Segmentation fault (core dumped) $ gdb fgfs (...) Core was generated by `fgfs'. Program terminated with signal 11, Segmentation faul