Why fatal log throw object.Error@(0) on console?
    Suliman via Digitalmars-d-learn 
    digitalmars-d-learn at puremagic.com
       
    Mon Jan 30 04:19:03 PST 2017
    
    
  
import std.stdio;
import std.experimental.logger;
void main()
{
	sharedLog = new FileLogger("New_Default_Log_File.log");
	fatal("Fatal error: ");
}
All other log-levels write as expected log files, but `fatal` 
throw on console:
> app.exe
object.Error@(0): A fatal log message was logged
----------------
0x0041291E
0x004138E7
0x0040206C
0x0040B277
0x0040B178
0x00407AB3
0x73FC62C4 in BaseThreadInitThunk
0x77440FD9 in RtlSubscribeWnfStateChangeNotification
0x77440FA4 in RtlSubscribeWnfStateChangeNotification
It's bug normal behavoiur?
    
    
More information about the Digitalmars-d-learn
mailing list