Re: [Flightgear-devel] 747 segfault

2003-01-08 Thread Major A

  #1 ssgSGIHeader::ssgSGIHeader(...

/usr/local/FlightGear/lib/FlightGear/Aircraft/747/Models/boeing747-400-jw-08.rgb, 
...)
at ssgLoadSGI.cxx:328
 
 This is plib crashing while trying to load a texture file.  My guess
 is that something is wrong with this texture.  Either it doesn't
 exist, or is corrupt.  Try updating your base package.

OK, thanks a lot, Andy! I wonder why cvs never updated that file --
after deleting it and updating the directory from cvs, it now works
fine.

  Andras

===
Major Andras
e-mail: [EMAIL PROTECTED]
www:http://andras.webhop.org/
===

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



Re: [Flightgear-devel] 747 segfault

2003-01-06 Thread Andy Ross
Matthew Johnson wrote:
 Major A wrote:
  does the 747-yasim segfault fgfs on everyone's computer?

 Yes I get a segfault too

I can't reproduce this with the command line solver (and can't run
fgfs from work).  Crashes in YASim are (well, have been) almost always
in the parser, and happen due to unhandled syntax errors.  Are you
sure you have the proper base package and an unmodified 747.xml file?

Can one of you get a stack trace in gdb to see where it's crashing?

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] 747 segfault

2003-01-06 Thread Curtis L. Olson
Andy Ross writes:
 I can't reproduce this with the command line solver (and can't run
 fgfs from work).  Crashes in YASim are (well, have been) almost always
 in the parser, and happen due to unhandled syntax errors.  Are you
 sure you have the proper base package and an unmodified 747.xml file?
 
 Can one of you get a stack trace in gdb to see where it's crashing?

The 747 is working for me right now in the CVS version.

Curt.
-- 
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] 747 segfault

2003-01-06 Thread Jim Wilson
Curtis L. Olson [EMAIL PROTECTED] said:

 Andy Ross writes:
  I can't reproduce this with the command line solver (and can't run
  fgfs from work).  Crashes in YASim are (well, have been) almost always
  in the parser, and happen due to unhandled syntax errors.  Are you
  sure you have the proper base package and an unmodified 747.xml file?
  
  Can one of you get a stack trace in gdb to see where it's crashing?
 
 The 747 is working for me right now in the CVS version.
 

Same here.  The other segfault that was reported might be the same as one I've
seen occur here lately (AFAIK any aircraft).  Currently I'm guessing it is
sound related,  but haven't yet found a way to make it happen regular enough
to get a stack trace.  It tends to happen either right at startup or on
landing (when there can be a lot of sounds going off).

Best,

Jim

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



Re: [Flightgear-devel] 747 segfault

2003-01-06 Thread Major A

 Can one of you get a stack trace in gdb to see where it's crashing?

This is the command line:

  /usr/local/FlightGear/bin/fgfs --fg-root=/usr/local/FlightGear/lib/FlightGear 
--aircraft=747

This is what gdb says:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 1137)]
0x08401482 in ssgSGIHeader::getRow (this=0x8f10ce0, buf=0x8f19cb8 '\004' repeats 200 
times..., y=862, z=3) at ssgLoadSGI.cxx:211
211   *bufp++ = *tmpp++ ;
(gdb) bt
#0  0x08401482 in ssgSGIHeader::getRow (this=0x8f10ce0, buf=0x8f19cb8 '\004' repeats 
200 times..., y=862, z=3) at ssgLoadSGI.cxx:211
#1  0x084017eb in ssgSGIHeader::ssgSGIHeader (this=0x8f10ce0, fname=0x8e5b0d0 
/usr/local/FlightGear/lib/FlightGear/Aircraft/747/Models/boeing747-400-jw-08.rgb, 
info=0xbfffce50) at ssgLoadSGI.cxx:328
#2  0x08401c85 in ssgLoadSGI (fname=0x8e5b0d0 
/usr/local/FlightGear/lib/FlightGear/Aircraft/747/Models/boeing747-400-jw-08.rgb, 
info=0xbfffce50) at ssgLoadSGI.cxx:496
#3  0x0840094b in ssgLoadTexture (filename=0x8e5b0d0 
/usr/local/FlightGear/lib/FlightGear/Aircraft/747/Models/boeing747-400-jw-08.rgb, 
info=0xbfffce50)
at ssgLoadTexture.cxx:301
#4  0x083fdd3a in ssgTexture::ssgTexture (this=0x8e5b090, fname=0xbfffceb0 
/usr/local/FlightGear/lib/FlightGear/Aircraft/747/Models/boeing747-400-jw-08.rgb, 
_wrapu=1, _wrapv=1, _mipmap=1) at ssgTexture.cxx:139
#5  0x0843aa07 in ssgLoaderOptions::createTexture (this=0x88d5740, tfname=0x8e5ae20 
boeing747-400-jw-08.rgb, wrapu=1, wrapv=1, mipmap=1) at ssgLoad.cxx:117
#6  0x083f1794 in get_state (mat=0x8e5aa68) at ssgLoadAC.cxx:220
#7  0x083f2aa3 in do_refs (s=0xbfffd7fd 3\n) at ssgLoadAC.cxx:579
#8  0x083f163c in search (tags=0x84b4f70, s=0xbfffd7fd 3\n) at ssgLoadAC.cxx:129
#9  0x083f2219 in do_surf (s=0xbfffdc7d 0x10\n) at ssgLoadAC.cxx:497
#10 0x083f163c in search (tags=0x84b4f60, s=0xbfffdc7d 0x10\n) at ssgLoadAC.cxx:129
#11 0x083f2175 in do_numsurf (s=0xbfffe0f0 6\n) at ssgLoadAC.cxx:484
#12 0x083f163c in search (tags=0x84b4f00, s=0xbfffe0f0 6\n) at ssgLoadAC.cxx:129
#13 0x083f1c29 in do_object () at ssgLoadAC.cxx:322
#14 0x083f163c in search (tags=0x84b4ee0, s=0xbfffe56f poly\n) at ssgLoadAC.cxx:129
#15 0x083f1c62 in do_object () at ssgLoadAC.cxx:330
#16 0x083f163c in search (tags=0x84b4ee0, s=0xbfffe9ef world\n) at ssgLoadAC.cxx:129
#17 0x083f2e70 in ssgLoadAC (fname=0x88f0d70 
Aircraft/747/Models/boeing747-400-jw.ac, options=0x0) at ssgLoadAC.cxx:676
#18 0x083f2c27 in ssgLoadAC3D (fname=0x88f0d70 
Aircraft/747/Models/boeing747-400-jw.ac, options=0x0) at ssgLoadAC.cxx:601
#19 0x0843ac4f in ssgLoad (fname=0x88f0d70 Aircraft/747/Models/boeing747-400-jw.ac, 
options=0x0) at ssgLoad.cxx:223
#20 0x082ddc40 in fgLoad3DModel (path=@0xb854) at model.cxx:281
#21 0x082e0a41 in FGModelPlacement::init (this=0x8e5a070, path=@0xb854) at 
model.cxx:639
#22 0x082e2377 in FGAircraftModel::init (this=0x8e59f08) at acmodel.cxx:57
#23 0x08055216 in fgMainInit (argc=3, argv=0xb9b4) at main.cxx:1658
#24 0x08056696 in main (argc=3, argv=0xb9b4) at main.cxx:1818

Other than that, I am running both FlightGear and fgfsbase from CVS
(Root is
:pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 and
:pserver:[EMAIL PROTECTED]:/home/cvsroot, respectively), no
modifications. I haven't updated plib and SimGear in a while though.

Hope this helps,

  Andras

===
Major Andras
e-mail: [EMAIL PROTECTED]
www:http://andras.webhop.org/
===

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



Re: [Flightgear-devel] 747 segfault

2003-01-06 Thread Matthew Johnson
Works fine on SuSE 8.1, after CVS update. Well apart from a blank
panel...

Matt
PS Build also went through without a hitch.

On Mon, 2003-01-06 at 15:58, Major A wrote:
  Can one of you get a stack trace in gdb to see where it's crashing?
 
 This is the command line:
 
   /usr/local/FlightGear/bin/fgfs --fg-root=/usr/local/FlightGear/lib/FlightGear 
--aircraft=747
 
 This is what gdb says:
 
 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 16384 (LWP 1137)]
 0x08401482 in ssgSGIHeader::getRow (this=0x8f10ce0, buf=0x8f19cb8 '\004' repeats 
200 times..., y=862, z=3) at ssgLoadSGI.cxx:211
 211   *bufp++ = *tmpp++ ;
 (gdb) bt
 #0  0x08401482 in ssgSGIHeader::getRow (this=0x8f10ce0, buf=0x8f19cb8 '\004' 
repeats 200 times..., y=862, z=3) at ssgLoadSGI.cxx:211
 #1  0x084017eb in ssgSGIHeader::ssgSGIHeader (this=0x8f10ce0, fname=0x8e5b0d0 
/usr/local/FlightGear/lib/FlightGear/Aircraft/747/Models/boeing747-400-jw-08.rgb, 
 info=0xbfffce50) at ssgLoadSGI.cxx:328
 #2  0x08401c85 in ssgLoadSGI (fname=0x8e5b0d0 
/usr/local/FlightGear/lib/FlightGear/Aircraft/747/Models/boeing747-400-jw-08.rgb, 
info=0xbfffce50) at ssgLoadSGI.cxx:496
 #3  0x0840094b in ssgLoadTexture (filename=0x8e5b0d0 
/usr/local/FlightGear/lib/FlightGear/Aircraft/747/Models/boeing747-400-jw-08.rgb, 
info=0xbfffce50)
 at ssgLoadTexture.cxx:301
 #4  0x083fdd3a in ssgTexture::ssgTexture (this=0x8e5b090, fname=0xbfffceb0 
/usr/local/FlightGear/lib/FlightGear/Aircraft/747/Models/boeing747-400-jw-08.rgb, 
 _wrapu=1, _wrapv=1, _mipmap=1) at ssgTexture.cxx:139
 #5  0x0843aa07 in ssgLoaderOptions::createTexture (this=0x88d5740, tfname=0x8e5ae20 
boeing747-400-jw-08.rgb, wrapu=1, wrapv=1, mipmap=1) at ssgLoad.cxx:117
 #6  0x083f1794 in get_state (mat=0x8e5aa68) at ssgLoadAC.cxx:220
 #7  0x083f2aa3 in do_refs (s=0xbfffd7fd 3\n) at ssgLoadAC.cxx:579
 #8  0x083f163c in search (tags=0x84b4f70, s=0xbfffd7fd 3\n) at ssgLoadAC.cxx:129
 #9  0x083f2219 in do_surf (s=0xbfffdc7d 0x10\n) at ssgLoadAC.cxx:497
 #10 0x083f163c in search (tags=0x84b4f60, s=0xbfffdc7d 0x10\n) at ssgLoadAC.cxx:129
 #11 0x083f2175 in do_numsurf (s=0xbfffe0f0 6\n) at ssgLoadAC.cxx:484
 #12 0x083f163c in search (tags=0x84b4f00, s=0xbfffe0f0 6\n) at ssgLoadAC.cxx:129
 #13 0x083f1c29 in do_object () at ssgLoadAC.cxx:322
 #14 0x083f163c in search (tags=0x84b4ee0, s=0xbfffe56f poly\n) at ssgLoadAC.cxx:129
 #15 0x083f1c62 in do_object () at ssgLoadAC.cxx:330
 #16 0x083f163c in search (tags=0x84b4ee0, s=0xbfffe9ef world\n) at 
ssgLoadAC.cxx:129
 #17 0x083f2e70 in ssgLoadAC (fname=0x88f0d70 
Aircraft/747/Models/boeing747-400-jw.ac, options=0x0) at ssgLoadAC.cxx:676
 #18 0x083f2c27 in ssgLoadAC3D (fname=0x88f0d70 
Aircraft/747/Models/boeing747-400-jw.ac, options=0x0) at ssgLoadAC.cxx:601
 #19 0x0843ac4f in ssgLoad (fname=0x88f0d70 
Aircraft/747/Models/boeing747-400-jw.ac, options=0x0) at ssgLoad.cxx:223
 #20 0x082ddc40 in fgLoad3DModel (path=@0xb854) at model.cxx:281
 #21 0x082e0a41 in FGModelPlacement::init (this=0x8e5a070, path=@0xb854) at 
model.cxx:639
 #22 0x082e2377 in FGAircraftModel::init (this=0x8e59f08) at acmodel.cxx:57
 #23 0x08055216 in fgMainInit (argc=3, argv=0xb9b4) at main.cxx:1658
 #24 0x08056696 in main (argc=3, argv=0xb9b4) at main.cxx:1818
 
 Other than that, I am running both FlightGear and fgfsbase from CVS
 (Root is
 :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 and
 :pserver:[EMAIL PROTECTED]:/home/cvsroot, respectively), no
 modifications. I haven't updated plib and SimGear in a while though.
 
 Hope this helps,
 
   Andras
 
 ===
 Major Andras
 e-mail: [EMAIL PROTECTED]
 www:http://andras.webhop.org/
 ===
 
 ___
 Flightgear-devel mailing list
 [EMAIL PROTECTED]
 http://mail.flightgear.org/mailman/listinfo/flightgear-devel
-- 
Matthew Johnson

Public Key

9560 AE15 A443 7FE5 E927  84D2 CD17 CF25 405C B240



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



Re: [Flightgear-devel] 747 segfault

2003-01-06 Thread Andy Ross
Major A wrote:
 #0 ssgSGIHeader::getRow() at ssgLoadSGI.cxx:211
 #1 ssgSGIHeader::ssgSGIHeader(...
   
/usr/local/FlightGear/lib/FlightGear/Aircraft/747/Models/boeing747-400-jw-08.rgb, 
...)
   at ssgLoadSGI.cxx:328

This is plib crashing while trying to load a texture file.  My guess
is that something is wrong with this texture.  Either it doesn't
exist, or is corrupt.  Try updating your base package.

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