Home/ Questions/Q 6886755
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T05:47:57+00:00

I’m working on some code that uses error_log() for debugging. The problem is that

  • 0

I’m working on some code that uses error_log() for debugging. The problem is that for some reason, all of the line breaks in the output appear as literal \n strings, so there’s no actual line break (making it damn near impossible to comprehend complex arrays).
I tried using both var_export and print_r with the error_log function, and both led to the same result: a block of text with \n scattered throughout. I even tried doing str_replace \n to PHP_EOL with no success. What am I doing wrong?

To clarify: the \n strings appear in the Console error log viewer, TextEdit, and the Terminal.

EDIT

Just wanted to note in advance that yes, I’m aware that you need to double-quote \n strings for them to appear as line breaks. However, I’m dealing with the output from print_r or var_export (to inspect an array) so this doesn’t really help me (I think?).

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Apparently, this issue is independent of your operating system. See this question: PHP error log and newline chars

    …you should be able to change the error_log directive in your php.ini on Debian to point to a file. If this is undefined, it will go through syslog which doesn’t support multiple lines.

    • 0