[GH-ISSUE #376] Monolog segfault with BIG message. #131

New issue

Closed

opened 2026-03-04 02:12:27 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 02:12:27 +03:00

Owner

Originally created by @lyrixx on GitHub (Jun 12, 2014).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/376

Of course, It's a bad idea to log BIG message, I will remove this log call from my code.
But this call github.com/Seldaek/monolog@25b16e8019/src/Monolog/Formatter/LineFormatter.php (L111) can segfault.

The same issue appear in Symfony few month ago, see https://github.com/symfony/symfony/pull/10231

Originally created by @lyrixx on GitHub (Jun 12, 2014). Original GitHub issue: https://github.com/Seldaek/monolog/issues/376 Of course, It's a bad idea to log BIG message, I will remove this log call from my code. But this call https://github.com/Seldaek/monolog/blob/25b16e801979098cb2f120e697bfce454b18bf23/src/Monolog/Formatter/LineFormatter.php#L111 can segfault. The same issue appear in Symfony few month ago, see https://github.com/symfony/symfony/pull/10231

kerem

2026-03-04 02:12:27 +03:00

closed this issue
added the
Bug
label

kerem commented

2026-03-04 02:12:28 +03:00

Author

Owner

@Seldaek commented on GitHub (Jun 15, 2014):

Did you actually experience it segfaulting? Because unless you have really a laaarge set of blank lines in the message I think that regex should do ok, it's very simple.

@Seldaek commented on GitHub (Jun 15, 2014): Did you actually experience it segfaulting? Because unless you have really a laaarge set of blank lines in the message I think that regex should do ok, it's very simple.

kerem commented

2026-03-04 02:12:28 +03:00

Author

Owner

@Seldaek commented on GitHub (Jun 15, 2014):

Besides I am not so sure what else we could do, except maybe a dumber str_replace in case the strlen() is bigger than X

@Seldaek commented on GitHub (Jun 15, 2014): Besides I am not so sure what else we could do, except maybe a dumber str_replace in case the strlen() is bigger than X

kerem commented

2026-03-04 02:12:28 +03:00

Author

Owner

@lyrixx commented on GitHub (Jun 15, 2014):

yes, yes. I did experience this segault (on prod). I use this hack to find the segfault, then I commented the line, and then everything went fine.

But as PHP died, I not sure about the line. But in the output, The lastes calls were inside monolog

@lyrixx commented on GitHub (Jun 15, 2014): yes, yes. I did experience this segault (on prod). I use this [hack](https://gist.github.com/lyrixx/17074868cdfabd4c783e) to find the segfault, then I commented the line, and then everything went fine. But as PHP died, I not sure about the line. But in the output, The lastes calls were inside monolog