Re: [Flightgear-devel] Communicating with IVAO client
On Dec 11, 2007 8:44 PM, Csaba Halász <[EMAIL PROTECTED]> wrote: > On Dec 11, 2007 8:29 PM, Roy Vegard Ovesen <[EMAIL PROTECTED]> wrote: > > > In any case I > > get a similar error and I of course do not have your IVAO code, so it might > > not be your fault after all. > > Me too. Apparently since Tim's osg pager changes. Ignore that. A complete rebuild of osg solved it. So much for cmake, thank you :( I should really have a look at the ccache thing. Sorry for the false alarm. -- Csaba/Jester - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Communicating with IVAO client
Roy Vegard Ovesen escribió: > I'm getting a very similar error when I exit fgfs: > > *** glibc detected *** build_sdl/src/Main/fgfs: corrupted double-linked list: > 0x00d4bcb0 *** > === Backtrace: = > /lib/libc.so.6[0x2ae1dcd46067] > /lib/libc.so.6[0x2ae1dcd47921] > /lib/libc.so.6(cfree+0x8c)[0x2ae1dcd4b6fc] > /usr/local/lib64/libosg.so.25(_ZN3osg8StateSetD0Ev+0x2d9)[0x2ae1d9efb0f9] > build_sdl/src/Main/fgfs[0x4e71d3] > build_sdl/src/Main/fgfs[0x4e7261] > ... > ... > > And this is with the CVS version. > >> I assume I've made some mistake, as I'm not familiar with FG >> architecture. What I've done exactly is to download the latest stable >> source code (0.9.11), and added/edited these few files before compiling, >> wich I'm attaching in this mail. I've attached as well the terminal >> command-line used and the resulting messages. > > You seem to be contradicting yourself here as I believe the latest stable, or > release, is 0.9.10. Perhaps you mean the 0.9.11-pre1 version. In any case I > get a similar error and I of course do not have your IVAO code, so it might > not be your fault after all. > > Yes, sorry, I just poured the word "stable" without much thinking. I really ment the 0.9.11-pre1. Thanks for your reply. Now I know I don't have to worry too much about my files. Best, Pep. - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Communicating with IVAO client
On Dec 11, 2007 8:29 PM, Roy Vegard Ovesen <[EMAIL PROTECTED]> wrote: > On Tuesday 11 December 2007, Pep Ribal wrote: > > With this new build I experience a small problem: as it works perfectly > > well with the --ivao option, sending the right packets, when it comes to > > shutdown FG, an error dump appears in my terminal window. However, if I > > run FG without the --ivao option, no error is produced. > > I'm getting a very similar error when I exit fgfs: > In any case I > get a similar error and I of course do not have your IVAO code, so it might > not be your fault after all. Me too. Apparently since Tim's osg pager changes. -- Csaba/Jester - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Communicating with IVAO client
On Tuesday 11 December 2007, Pep Ribal wrote: > With this new build I experience a small problem: as it works perfectly > well with the --ivao option, sending the right packets, when it comes to > shutdown FG, an error dump appears in my terminal window. However, if I > run FG without the --ivao option, no error is produced. I'm getting a very similar error when I exit fgfs: *** glibc detected *** build_sdl/src/Main/fgfs: corrupted double-linked list: 0x00d4bcb0 *** === Backtrace: = /lib/libc.so.6[0x2ae1dcd46067] /lib/libc.so.6[0x2ae1dcd47921] /lib/libc.so.6(cfree+0x8c)[0x2ae1dcd4b6fc] /usr/local/lib64/libosg.so.25(_ZN3osg8StateSetD0Ev+0x2d9)[0x2ae1d9efb0f9] build_sdl/src/Main/fgfs[0x4e71d3] build_sdl/src/Main/fgfs[0x4e7261] ... ... And this is with the CVS version. > I assume I've made some mistake, as I'm not familiar with FG > architecture. What I've done exactly is to download the latest stable > source code (0.9.11), and added/edited these few files before compiling, > wich I'm attaching in this mail. I've attached as well the terminal > command-line used and the resulting messages. You seem to be contradicting yourself here as I believe the latest stable, or release, is 0.9.10. Perhaps you mean the 0.9.11-pre1 version. In any case I get a similar error and I of course do not have your IVAO code, so it might not be your fault after all. -- Roy Vegard Ovesen - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Communicating with IVAO client
I'm developing a client application for the IVAO network. John Wojnaroski sent me some time ago a few files to be added/changed in Flightgear source code so that FG sends UDP packets to my application. I've done some changes to these files as well. Now I've changed to Fedora 8, and I've made a complete rebuild of Flightgear. With the modifiations made with John, FG results in having an option namely --ivao. With this new build I experience a small problem: as it works perfectly well with the --ivao option, sending the right packets, when it comes to shutdown FG, an error dump appears in my terminal window. However, if I run FG without the --ivao option, no error is produced. I assume I've made some mistake, as I'm not familiar with FG architecture. What I've done exactly is to download the latest stable source code (0.9.11), and added/edited these few files before compiling, wich I'm attaching in this mail. I've attached as well the terminal command-line used and the resulting messages. If someone could take a look and see if it's a problem in the files, it would really help. Thanks a lot. Pep Ribal. FG-IVAO files.tar.gz Description: GNU Zip compressed data [EMAIL PROTECTED] ~]$ fgfs --airport=BIVM --ivao=socket,out,10,192.168.1.3,6000,udp Model Author: Unknown Creation Date: 2002-01-01 Version: $Id: c172p.xml,v 1.18 2007-01-15 12:50:45 ehofman Exp $ Description: Cessna C-172 Initializing Nasal Electrical System power up *** glibc detected *** fgfs: corrupted double-linked list: 0x08db5b70 *** === Backtrace: = /lib/libc.so.6[0xa92d5d] /lib/libc.so.6[0xa947fb] /lib/libc.so.6(cfree+0x90)[0xa980f0] /usr/lib/libGL.so.1[0x724469a] === Memory map: 00101000-00105000 r-xp 08:05 3489157/usr/lib/libXxf86vm.so.1.0.0 00105000-00106000 rwxp 3000 08:05 3489157/usr/lib/libXxf86vm.so.1.0.0 0011-00111000 r-xp 0011 00:00 0 [vdso] 00111000-0012c000 r-xp 08:05 3480043/usr/lib/libplibpuaux.so.1.8.4 0012c000-0012d000 rwxp 0001b000 08:05 3480043/usr/lib/libplibpuaux.so.1.8.4 0012d000-00158000 r-xp 08:05 3479954/usr/lib/libplibpu.so.1.8.4 00158000-0015a000 rwxp 0002b000 08:05 3479954/usr/lib/libplibpu.so.1.8.4 0015a000-00167000 r-xp 08:05 3479923/usr/lib/libplibfnt.so.1.8.4 00167000-00169000 rwxp d000 08:05 3479923/usr/lib/libplibfnt.so.1.8.4 00169000-0016a000 rwxp 00169000 00:00 0 0016a000-0016c000 r-xp 08:05 3479926/usr/lib/libplibjs.so.1.8.4 0016c000-0016d000 rwxp 1000 08:05 3479926/usr/lib/libplibjs.so.1.8.4 0016d000-00174000 r-xp 08:05 3479927/usr/lib/libplibnet.so.1.8.4 00174000-00175000 rwxp 7000 08:05 3479927/usr/lib/libplibnet.so.1.8.4 00175000-0019e000 r-xp 08:05 3480175/usr/lib/libplibssgaux.so.1.8.4 0019e000-001a8000 rwxp 00029000 08:05 3480175/usr/lib/libplibssgaux.so.1.8.4 001a8000-00244000 r-xp 08:05 3480142/usr/lib/libplibssg.so.1.8.4 00244000-00249000 rwxp 0009c000 08:05 3480142/usr/lib/libplibssg.so.1.8.4 00249000-00506000 rwxp 00249000 00:00 0 00506000-00517000 r-xp 08:05 3480048/usr/lib/libplibsg.so.1.8.4 00517000-00518000 rwxp 0001 08:05 3480048/usr/lib/libplibsg.so.1.8.4 00518000-0051c000 r-xp 08:05 3480180/usr/lib/libplibul.so.1.8.4 0051c000-0051d000 rwxp 3000 08:05 3480180/usr/lib/libplibul.so.1.8.4 0051d000-0054d000 r-xp 08:05 3479843/usr/lib/libglut.so.3.8.0 0054d000-00552000 rwxp 0002f000 08:05 3479843/usr/lib/libglut.so.3.8.0 00552000-00557000 r-xp 08:05 3479710/usr/lib/libalut.so.0.1.0 00557000-0055a000 rwxp 4000 08:05 3479710/usr/lib/libalut.so.0.1.0 0055a000-00595000 r-xp 08:05 3474997/usr/lib/libopenal.so.0.0.0 00595000-00596000 rwxp 0003b000 08:05 3474997/usr/lib/libopenal.so.0.0.0 00596000-0059a000 rwxp 00596000 00:00 0 0059a000-0059b000 r-xp 08:05 3481986/usr/lib/libxcb-xlib.so.0.0.0 0059b000-0059c000 rwxp 08:05 3481986/usr/lib/libxcb-xlib.so.0.0.0 0059c000-005b7000 r-xp 08:05 3481996/usr/lib/libxcb.so.1.0.0 005b7000-005b8000 rwxp 0001a000 08:05 3481996/usr/lib/libxcb.so.1.0.0 005b8000-005ba000 rwxp 00:10 197/dev/zero 0082a000-00898000 r-xp 08:05 3480095/usr/lib/libSDL-1.2.so.0.11.1 00898000-0089a000 rwxp 0006e000 08:05 3480095/usr/lib/libSDL-1.2.so.0.11.1 0089a000-008c5000 rwxp 0089a000 00:00 0 008ea000-0093e000 r-xp 08:05 3488432/usr/lib/libXt.so.6.0.0 0093e000-00942000 rwxp 00054000 08:05 3488432/usr/lib/libXt.so.6.0.0 00944000-0095a000 r-xp 08:05 3488580/usr/lib/libXmu.so.6.2.0 0095a000-0095b000 rwxp 00016000 08:05 3488580/usr/lib/libXmu.so.6.2.0 00a08000-00a23000 r-xp 08:05 1049560/lib/ld-2.7.so 00a23000-00a24000 r-xp 0001a000 08:05 1049560/lib/ld-2.7.so 00a24000-00a25000 rwxp 0001b000 08:05 1049560/lib/ld-2.7.so 00a27000-00a2800
