THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below.
User who did this: - Steve Reinhardt (stever) Attached to Project - M5 Bugs Summary - report failure on opening output files Task Type - Bug Category - Global/Other Status - New Assigned To - Operating System - All Severity - Medium Priority - Normal Reported Version - 2.0beta5 Due in Version - Due Date - Undecided Details - In src/etherdump.cc, we open the output file by passing the path to the ofstream constructor and never check to see that the file opened correctly, resulting in a silent fail and confused users. I suspect that's not the only place we do that. We should check for success on the stream open and call fatal() if the open fails. (I'm for dying rather than merely warning since allowing a multi-hour simulation to run when it might not be generating the desired output sounds bad to me.) More information can be found at the following URL: http://www.m5sim.org/flyspray/task/312 You are receiving this message because you have requested it from the Flyspray bugtracking system. You can be removed from future notifications by visiting the URL shown above. _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
