Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|06284||Interface||Minor||Always||Jul 7, 2016, 04:09||Jul 8, 2016, 13:04|
|Tester||Tafoid||View Status||Public||Platform||MAME (Official Binary)|
|Assigned To||cuavas||Resolution||Fixed||OS||Windows Vista/7/8 (64-bit)|
|Version||0.175||Fixed in Version||0.176||Build||Normal|
|Summary||06284: Watchdog dialog is not able to be captured|
When you run a machine which triggers MAME's watchdog mechanism, you normally get a specific message "Terminating due to watchdog timeout" printed to let you know MAME has ceased operation because the machine was inactive for that watchdog duration. What is happening is that it shows but is not capture or doesn't even appear when text is redirected (captured) to a text file.
Inability to have these message captured make determining bugs more difficult as reason for exiting is never captured.
|Steps To Reproduce||
mame comg079 -bench 5 -watchdog 5
The following is output:
07-93.u7 ROM NEEDS REDUMP WARNING: the machine might not run correctly. Terminating due to watchdog timeout
mame comg079 -bench 5 -watchdog 5 > out.txt 2> out2.txt
The follow is captured in errout (out2.txt)
07-93.u7 ROM NEEDS REDUMP WARNING: the machine might not run cor
|Affected Sets / Systems|
|There are no relationship linked to this issue.|
Jul 7, 2016, 13:37
|This bug is probably Windows-specific: Windows, unlike POSIX, allows stderr to be buffered when redirected.|
Jul 7, 2016, 15:35
after line 36 of osd/watchdog.cpp fixes the problem, but I would like to have it confirmed by someone on Linux.
Jul 8, 2016, 06:50
|Should be fixed now. Can you try it again Tafoid?|
Jul 8, 2016, 13:03
Looks good testing with a fresh built binary with the above example.