In fgms 1.0.0-dev, loading fg_tracker module (i.e. "server.tracked = true" in conf file) will cause logic error
\===================
$ ./fgms
Could not read config file '/usr/etc/fgms.conf' => using defaults
Could not read config file '/home/tester/fgms.conf' => using defaults
processing fgms.conf
# using logfile /home/tester/scripts/dev/fgtracker/build-fgms-1-x/fgms.log
23.06.2017 19:40:39 # This is MPVESERVER15(mpserver15.flightgear.org)
23.06.2017 19:40:39 # FlightGear Multiplayer Server v1.0.0-dev started
23.06.2017 19:40:39 # using protocol version v1.1 (LazyRelay enabled)
23.06.2017 19:40:39 # listening to port 5003
23.06.2017 19:40:39 # telnet port 5004
23.06.2017 19:40:39 # admin port 5005
23.06.2017 19:40:39 # using logfile /home/tester/scripts/dev/fgtracker/build-fgms-1-x/fgms.log
23.06.2017 19:40:39 # listening on 10.130.10.172
23.06.2017 19:40:39 # tracked to 10.130.100.172:8000, using a thread.
23.06.2017 19:40:39 # I have 1 relays
23.06.2017 19:40:39 # relay 10.130.100.3:5000 (10.130.100.3)
23.06.2017 19:40:39 # I have 0 crossfeeds
23.06.2017 19:40:39 # I have 0 blacklisted IPs
23.06.2017 19:40:39 # Files: exit=[/tmp/fgms_exit] stat=[/tmp/fgms_stat]
23.06.2017 19:40:39 Main server started!
FlightGear Multiplayer Server CLI
This is MPVESERVER15 (mpserver15.flightgear.org)
------------------------------------------------
Username: terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_M_construct null not valid
Aborted
$
\===================
Diff:
fixed in commit bebeb7