Board index FlightGear Development New features

Segfaults: try your hand

Discussion and requests for new features. Please note that FlightGear developers are volunteers and may or may not be able to consider these requests.

Segfaults: try your hand

Postby polly » Fri Sep 23, 2022 6:06 pm

I'd appreciate if anyone can confirm a segfault, on next, with this command file:
Code: Select all
##
#--aircraft=c310dpm-3d
#
--aircraft=katana
###
#Aostsa     
--airport=LIMW
--runway=27
##
#
--fg-root=/fgfs/FlightGear
#
--fg-aircraft=/fgfs/fgdata/Aircraft:/fgfs/fgaddon/Aircraft
##
#
--terrasync-dir=/fgfs/scenTerr
#
--enable-terrasync
#
--fg-scenery=/fgfs/scenTerr
##
#
--timeofday=morning
--log-level=alert
###
###]


Essentially: Start at LIMW R27 with a YASim model. I've been seeing, and trying to pin down, a NaN error in YASim's figuring of contact points for gear elements. The segfaults appear after YASim's last logout and so the fgfs log can appear as if the segfault is a NaN, or a load error with building.png in the scenery, for example.
i can get a segfault consistently with the above command file, it happens during about the 4th or 5th iteration throught the gear loop, single stepping changes the symptom.

In appreciation here's a route map for the St Bernard to Sion, it's right, left, third right and a sharp right over an 8000ft pass. The route can ge loaded into e.g. the generic route manager for the PC-6 to have a map-follow available. It's a good test for your mixture handling in GA models.

Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<gpx xmlns="http://www.topografix.com/GPX/1/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" creator="SkyVector" version="1.1" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd">
  <rte>
    <name>SV001-SV026</name>
    <rtept lat="45.737770" lon="7.346609">
      <name>SV001</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="45.765200" lon="7.317083">
      <name>SV002</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="45.782393" lon="7.304531">
      <name>SV003</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="45.791461" lon="7.298737">
      <name>SV004</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="45.798193" lon="7.287407">
      <name>SV005</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="45.806182" lon="7.254693">
      <name>SV006</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="45.813768" lon="7.241484">
      <name>SV007</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="45.820826" lon="7.224232">
      <name>SV008</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="45.818494" lon="7.191788">
      <name>SV009</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="45.824954" lon="7.182003">
      <name>SV010</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="45.860829" lon="7.156254">
      <name>SV011</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="45.871766" lon="7.179428">
      <name>SV012</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="45.899906" lon="7.189728">
      <name>SV013</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="45.933584" lon="7.202345">
      <name>SV014</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="45.969568" lon="7.204920">
      <name>SV015</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="46.022875" lon="7.144152">
      <name>SV016</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="46.072558" lon="7.149559">
      <name>SV017</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="46.080239" lon="7.114540">
      <name>SV018</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="46.076845" lon="7.077976">
      <name>SV019</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="46.072736" lon="7.055574">
      <name>SV020</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="46.090240" lon="7.054029">
      <name>SV021</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="46.125587" lon="7.122522">
      <name>SV022</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="46.204001" lon="7.256744">
      <name>SV023</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="46.213267" lon="7.286957">
      <name>SV024</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="46.217780" lon="7.316139">
      <name>SV025</name>
      <overfly>false</overfly>
    </rtept>
    <rtept lat="46.223244" lon="7.339142">
      <name>SV026</name>
      <overfly>false</overfly>
    </rtept>

  </rte>
</gpx>


Thanks !
User avatar
polly
 
Posts: 956
Joined: Thu Nov 04, 2010 3:45 pm

Re: Segfaults: try your hand

Postby MariuszXC » Fri Sep 23, 2022 9:09 pm

Which commit id are you testing / having issue with? Is it some specific id, or a problem existing across multiple commits?
INOP
MariuszXC
 
Posts: 1061
Joined: Tue May 18, 2021 5:38 pm
Location: Europe
Callsign: SP-MRM
Version: 2020.4
OS: Ubuntu 16.04

Re: Segfaults: try your hand

Postby polly » Fri Sep 23, 2022 10:13 pm

Hi,
Today they will be pulls from 'next' no earlier than 21Sep but I've been seeing this for at least some months, since I was developing an application that automatically rewrites YASim configurations on the fly it's been difficault to sort the problem.
User avatar
polly
 
Posts: 956
Joined: Thu Nov 04, 2010 3:45 pm


Return to New features

Who is online

Users browsing this forum: No registered users and 5 guests