Re: [Flightgear-devel] Other segfaults -- the same? (was Re: segfault in AI code)
On 10/21/04 at 12:19 PM Chris Metzler wrote:
Here's what I see from gdb . . .
snip
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 3690)]
0x080b0705 in FGTower::ProcessDownwindReport (this=0xd041ee8, t=0xd87d8c8)
at AIPlane.hxx:80
80 inline PatternLeg GetLeg() {return leg;}
(gdb) backtrace
#0 0x080b0705 in FGTower::ProcessDownwindReport (this=0xd041ee8,
t=0xd87d8c8)
at AIPlane.hxx:80
#1 0x080af97c in FGTower::Respond (this=0xd041ee8) at tower.cxx:520
#2 0x080aee7d in FGTower::Update (this=0xd041ee8, dt=0.17272)
at tower.cxx:356
#3 0x0808d428 in FGATCMgr::update (this=0x98727e0, dt=0.034546)
at stl_list.h:167
#4 0x08052e20 in fgMainLoop () at globals.hxx:278
#5 0x08083dc5 in GLUTidle () at fg_os.cxx:114
#6 0x400a9c67 in glutMainLoop () from /usr/lib/libglut.so.3
#7 0x08054bd5 in fgMainInit (argc=9, argv=0xb570) at main.cxx:943
#8 0x0805166d in main (argc=0, argv=0x0) at bootstrap.cxx:185
Thanks, I've had problems with that bit of code before, I'll hopefully get
it tracked down now.
Cheers - Dave
This message has been scanned but we cannot guarantee that it and any
attachments are free from viruses or other damaging content: you are
advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Other segfaults -- the same? (was Re: segfault in AI code)
On Thu, 21 Oct 2004 09:06:14 -0500 David Culp [EMAIL PROTECTED] wrote: Just downloaded a fresh CVS FlightGear and found that the AI code is causing segfaults now. I'll recompile and run it through gdb. In the mean time beware that some aircraft that set up AI scenarios by default, like the T-38 or the hunter-2tanks, are crashing the sim. I've run it through gdb and didn't get any useful output. After a few hours of detective work with cout's I'm getting this: [EMAIL PROTECTED] bin]$ ./t38 FGPropertyManager::GetNode() No node found for fcs/throttle-cmd-norm[0] Creating new property FGPropertyManager::GetNode() No node found for fcs/throttle-cmd-norm[1] Creating new property Starting FGAIManager::bind() Finished FGAIManager::bind() Creating new scenario: refueling_demo Creating an AIAircraft Created an AIAircraft Scenario has been processed. ./t38: line 24: 662 Aborted /home/dave/bin/fgfs $cmdline The sim is crashing before the first call to FGAIManager::update(), however the init() is working fine, and the scenario gets processed and an AI aircraft is created properly. AFAIK the AI subsystem doesn't do anything else between bind() and update(), so the property system (as pointed out by Fred) might be a good place to look. Hmmm. I was having a problem that I was starting to write up the night before last, until I saw your post. I thought it was the same problem, and you'd reported it. But now I'm beginning to wonder if they *were* the same problem. I get the impression from the above that your segfaults are occuring promptly, at the beginning of the scenario. I'm getting segfaults that seem related to the AI subsystem. They occur when I turn AI traffic on through the menu. They seem more frequent as I turn the AI traffic density up from 1 to 3. But they don't occur promptly upon start; instead, they almost always occur when I'm on final for a landing. --log-level=debug shows no useful messages -- there's just an abrupt end. But if I don't enable the AI traffic, I don't get the segfaults. -c -- Chris Metzler [EMAIL PROTECTED] (remove snip-me. to email) As a child I understood how to give; I have forgotten this grace since I have become civilized. - Chief Luther Standing Bear pgpzeOeBaGdJt.pgp Description: PGP signature ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Other segfaults -- the same? (was Re: segfault in AI code)
I'm getting segfaults that seem related to the AI subsystem. They occur when I turn AI traffic on through the menu. They seem more frequent as I turn the AI traffic density up from 1 to 3. But they don't occur promptly upon start; instead, they almost always occur when I'm on final for a landing. --log-level=debug shows no useful messages -- there's just an abrupt end. But if I don't enable the AI traffic, I don't get the segfaults. That's strange because the AI subsystem and the AI Traffic subsystem are two different and completely seperate systems. Dave -- David Culp [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Other segfaults -- the same? (was Re: segfault in AI code)
On 10/21/04 at 9:52 AM David Culp wrote: I'm getting segfaults that seem related to the AI subsystem. They occur when I turn AI traffic on through the menu. They seem more frequent as I turn the AI traffic density up from 1 to 3. But they don't occur promptly upon start; instead, they almost always occur when I'm on final for a landing. --log-level=debug shows no useful messages -- there's just an abrupt end. But if I don't enable the AI traffic, I don't get the segfaults. That's strange because the AI subsystem and the AI Traffic subsystem are two different and completely seperate systems. Uggh, that's me in the firing line then! I haven't added any features or code to the AI-traffic system for quite a while, probably pre-0.9.5. I thought I had all the bugs worked out, but it seems not :-( It's been switched off by default for the last couple of versions so I guess that's why it hasn't been generating complaints before. Can you get a backtrace? Cheers - Dave This message has been scanned but we cannot guarantee that it and any attachments are free from viruses or other damaging content: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Other segfaults -- the same? (was Re: segfault in AI code)
On Thu, 21 Oct 2004 15:55:24 +0100
David Luff [EMAIL PROTECTED] wrote:
Uggh, that's me in the firing line then! I haven't added any features
or code to the AI-traffic system for quite a while, probably pre-0.9.5.
I thought I had all the bugs worked out, but it seems not :-( It's been
switched off by default for the last couple of versions so I guess
that's why it hasn't been generating complaints before. Can you get a
backtrace?
Here's what I see from gdb . . .
(gdb) run
Starting program: /home/cmetzler/Projects/FlightGear-0.9/source/src/Main/fgfs
--enable-fullscreen --prop:/environment/params/real-world-weather-fetch=true
--airport=KDCA --offset-azimuth=45 --offset-distance=7.0 --altitude=4000 --vc=100
--heading=0
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 3690)]
Failed to find runway 28R at airport KDCA
[New Thread 32769 (LWP 3693)]
[New Thread 16386 (LWP 3694)]
Object PanelInstruments not found
Object ControlsGroup not found
[New Thread 32771 (LWP 3696)]
[New Thread 49156 (LWP 3697)]
Altitude = 74
Temp at alt (C) = 11
Temp sea level (C) = 11.1425
Altitude = 74
Dewpoint at alt (C) = 11
Dewpoint at sea level (C) = 11.0148
Trim Results:
Angle of Attack: 0.44 wdot: 9.13e-06 Tolerance: 1e-03 Passed
Throttle: 0.75 udot: 8.47e-02 Tolerance: 1e-03 Failed
Pitch Trim: 0.22 qdot: 4.09e-03 Tolerance: 1e-04 Failed
Trim Statistics:
Total Iterations: 61
Sub-iterations:
wdot: 126 average: 2.07 successful: 57 stability: 3.96
udot: 1148 average: 18.82 successful: 1 stability: 14.47
qdot: 121 average: 1.98 successful: 61 stability: 4.26
Run Count: 22370
Altitude = 15
Temp at alt (C) = 12
Temp sea level (C) = 12.029
Altitude = 15
Dewpoint at alt (C) = 11
Dewpoint at sea level (C) = 11.003
Error: base = 0,858.14 course = 0.881677 dist = 8.88574e+06
Error: base = 0,-1099.45 course = 4.56981 dist = 8.88574e+06
Error: base = 0,857.26 course = 0.881679 dist = 8.88573e+06
Error: base = 0,-1099.45 course = 4.56981 dist = 8.88573e+06
Error: base = 0,857.261 course = 0.881681 dist = 8.88572e+06
Error: base = 0,-1098.97 course = 4.56898 dist = 8.88294e+06
Error: base = 0,855.813 course = 0.880004 dist = 8.88294e+06
Error: base = 0,-1098.97 course = 4.56898 dist = 8.88294e+06
Error: base = 0,855.808 course = 0.880004 dist = 8.88294e+06
Error: base = 0,-1099.38 course = 4.56978 dist = 8.88522e+06
Altitude = 74
Temp at alt (C) = 11
Temp sea level (C) = 11.1425
Altitude = 74
Dewpoint at alt (C) = 11
Dewpoint at sea level (C) = 11.0148
Altitude = 15
Temp at alt (C) = 12
Temp sea level (C) = 12.029
Altitude = 15
Dewpoint at alt (C) = 11
Dewpoint at sea level (C) = 11.003
Altitude = 280
Temp at alt (C) = 11
Temp sea level (C) = 11.5399
Altitude = 280
Dewpoint at alt (C) = 11
Dewpoint at sea level (C) = 11.056
Altitude = 15
Temp at alt (C) = 12
Temp sea level (C) = 12.029
Altitude = 15
Dewpoint at alt (C) = 11
Dewpoint at sea level (C) = 11.003
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 3690)]
0x080b0705 in FGTower::ProcessDownwindReport (this=0xd041ee8, t=0xd87d8c8)
at AIPlane.hxx:80
80 inline PatternLeg GetLeg() {return leg;}
(gdb) backtrace
#0 0x080b0705 in FGTower::ProcessDownwindReport (this=0xd041ee8, t=0xd87d8c8)
at AIPlane.hxx:80
#1 0x080af97c in FGTower::Respond (this=0xd041ee8) at tower.cxx:520
#2 0x080aee7d in FGTower::Update (this=0xd041ee8, dt=0.17272)
at tower.cxx:356
#3 0x0808d428 in FGATCMgr::update (this=0x98727e0, dt=0.034546)
at stl_list.h:167
#4 0x08052e20 in fgMainLoop () at globals.hxx:278
#5 0x08083dc5 in GLUTidle () at fg_os.cxx:114
#6 0x400a9c67 in glutMainLoop () from /usr/lib/libglut.so.3
#7 0x08054bd5 in fgMainInit (argc=9, argv=0xb570) at main.cxx:943
#8 0x0805166d in main (argc=0, argv=0x0) at bootstrap.cxx:185
HTH.
-c
--
Chris Metzler [EMAIL PROTECTED]
(remove snip-me. to email)
As a child I understood how to give; I have forgotten this grace since I
have become civilized. - Chief Luther Standing Bear
pgpkRWhsT03So.pgp
Description: PGP signature
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
