Is flightgear 3.4 compatible with mesa 11 ?

[Curtis]

thank you Bugman and Hooray

I will try to download the RC version of flightgear in order to test it ( currently I use only the 3.4 version )

[hamzaalloush]

Curtis, if you want a reproducible established error to get your feet wet outside of Mesa, i had back luck logging to multiple files in FGFS with a segfault, i understand that you might not be interested in this though, i deal with GDB even though i'm not really familiar with the results of the output, i can only forward to people with experience, maybe even in C++

http://forum.flightgear.org/viewtopic.php?f=36&t=27583#p259476

[Curtis]

Ok I will try to reproduce this bug in the next few days,

I know a little C++ ( the basis, create a class, understanding the algorithm ) but some aspects can be difficult to handle ( templates, pointers, threads mutex/lock ), my favourite language is in fact java,

but it's not really a problem, the more important is to be able to reproduce the bug, and then try to find a good strategy in order to catch the culprit, git-bisect, gdb can help to isolate the faulty function, putting breakpoints will help also for checking the algorithm and the values of some variables

[hamzaalloush]

wouldn't want to derail the thread, but $fgsrc/docs-mini/README.logging advertises the ability to do multiple logs, anyway i reproduce with puting this .xml in my .fgfs directory, this is $FG_HOME for Linux, if you are using other platforms might be different, so put this "mylog.xml" file in $FG_HOME (.fgfs on Linux).

mylog.xml

Code: Select all

PropertyList>
   <logging>
      <log n="0">
         <enabled type="bool">true</enabled>
         <interval-ms type="long">1000</interval-ms>
         <filename>frameSpacing.csv</filename>
         <delimiter> </delimiter>
            <entry n="0">
               <enabled type="bool">true</enabled>
               <title>frameSpacing</title>
               <property>/sim/frame-latency-max-ms</property>
            </entry>
      </log>
      <log n="1">
         <enabled type="bool">true</enabled>
         <interval-ms type="long">1000</interval-ms>
         <filename>actualFPS.csv</filename>
         <delimiter> </delimiter>
            <entry n="0">
               <enabled type="bool">true</enabled>
               <title>actualFPS</title>
               <property>/sim/frame-rate</property>
            </entry>
      </log>
      <log n="2">
          <enabled type="bool">true</enabled>
          <interval-ms type="long">1000</interval-ms>
          <filename>worstFPS.csv</filename>
          <delimiter> </delimiter>
             <entry n="0">
                <enabled type="bool">true</enabled>
                <title>worstFPS</title>
                <property>/sim/frame-rate-worst</property>
             </entry>
      </log>
   </logging>
</PropertyList>

.fgfs --config=/home/<username>/.fgfs/mylog.xml

then, boom! segault

this is as far as i will go to hijack this thread, sorry, please continue, the original topic over here: http://forum.flightgear.org/viewtopic.php?f=36&t=27583