Re: Error Log Files

Have you checked your server logs? If the compilation error happens before the fatalsToBrowser were compiled, the error doesn't go to the browser.

"\n" just adds a newline. If there was no newline on the preceding line, it doesn't create a blank line. You need two newlines for that.

print 'first line';
print "\n";
print 'second line';
print "\n\n";
print 'fourth line';
[download]

($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,
[download]

Comment on Re: Error Log Files Select or Download Code

Replies are listed 'Best First'.
Re^2: Error Log Files by tultalk (Monk) on Mar 07, 2017 at 15:15 UTC
I am assuming that this code compiles and resides in memory and each time an error or warn is captured it is sent through carpout to be printed. So if I put print "\n\n"; after the carpout call, it should insert a blank line. However, based on the next monk response, carpout does not work that way and output the whole black of error in one shot and the blank is added befor eor after the block depending location of the \n\n code.	[reply]
Re^3: Error Log Files by 1nickt (Canon) on Mar 07, 2017 at 15:41 UTC
So if I put print "\n\n"; after the carpout call, it should insert a blank line. What in the documentation for carpout supports that idea? More doc, less assuming! Since the BEGIN block is executed at the beginning only, as explained in its documentation, maybe what you are thinking of is a custom sig handler for warn? The way forward always starts with a minimal test.	[reply]
Re^4: Error Log Files by tultalk (Monk) on Mar 07, 2017 at 17:14 UTC
So basically it opens a path to "mylogfile" where the errors are written so obviously \n\n is meaning less in this case. Adding blank lines would have to take place in the actual module code. Ug!! Read and UNDERSTAND documentation. Thanks	[reply]
Re^2: Error Log Files by tultalk (Monk) on Mar 07, 2017 at 15:25 UTC
You said: Have you checked your server logs? If the compilation error happens before the fatalsToBrowser were compiled, the error doesn't go to the browser. I ust checked server logs and nothing there. Not even stuff that was reported in my own error log. Will this block intercept errors and prevent them from reaching the regular server log?	[reply]