Hi, there is currently no option for flushing the log file (though maybe this should be the default anyway: https://github.com/eclipse/sumo/issues/12714) stdout and stderr are supposed to flush after every simulation step. So instead of using sumo-gui you could run sumo where the log goes to stdout/stderr However, the log file is rarely enough to diagnose a gui crash anyway. A reproducible example is needed instead. If there is no log file at all despite running with verbose, then possibly the simulation failed to start properly.
Am Di., 28. Feb. 2023 um 10:16 Uhr schrieb Ruud van Gaal < [email protected]>: > Hi, > > I'm investigating an issue on Windows where SUMO-GUI crashes at some > point. I don't get a log file though when it crashes. I run with these > arguments: > > > > > > > > > > > > > > > > > > *Starting SUMO with these arguments: sumo-gui -c > cruden_world_2.sumocfg --step-length 0.100000 --time-to-teleport -1 > --lanechange.duration 2.000000 --verbose true --log sumo_lastrun.log > --start --quit-on-end* > > When killing sumo-gui for example from the TaskManager, the > 'sumo_lastrun.log' file doesn't appear; so any last-minute exception that > might have occurred is lost. When closing normally, the log file is written > correctly. > > Is there a mode or argument to enforce a flush of the log file after each > message for example? > > Thanks, > Ruud > > _______________________________________________ > sumo-user mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user >
_______________________________________________ sumo-user mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
