Descriptive Problem Summary: The -verbose flag seems to have broken at some point and currently does nothing.
Make a new environment -- or use an existing one -- and create a verb that calls CRASH(). Use said verb repeatedly and observe. Takes less than a minute of repeated clicking to reproduce this issue.
Expected Results: I expect all runtime errors to print out all relevant information, regardless of how large the stack/output gets, when the -verbose flag is activated.
Actual Results: Runtime error information is eventually cropped off.
ID:2485067
 Jul 10 2019, 9:04 am (Edited on Jul 10 2019, 9:13 am)
|
|||||||||||||
Resolved
| |||||||||||||
|
Aug 18 2019, 1:19 am
|
|
FKI
 |
Bump.
|
Bump... still a problem. The server uses Windows Server 2008... if that matters.
| |
http://files.byondhome.com/FKI/Test%20Environment_src.zip
Put this together on my Windows 7 machine... spam the test() verb for 5 seconds. The data is first shortened, then not shown at all due to suppression. | |
Lummox JR changed status to 'Unverified'
| |
I ran this under DD with the -verbose argument and was not able to confirm your issue. Runtime errors continued regardless.
| |
Lummox JR resolved issue
| |