0001646: Missing newline in error message

ID	Project	Category	View Status	Date Submitted	Last Update
0001646	Xdebug	Uncategorized	public	2019-03-07 23:25	2019-04-05 10:48

Reporter	dwilks	Assigned To
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	2.6.0
Target Version	2.7.1	Fixed in Version	2.7.1

Summary	0001646: Missing newline in error message
Description	I don't know what's causing it yet but I'm seeing tons of broken socket error messages filling up Apache's error log. The worst part is that the error message doesn't have a newline `fprintf(stderr, "There was a problem sending %zd bytes on socket %d: %s", tmp->l, context->socket, sock_error);` so any tool I point at the error log goes nuts on lines that are megabytes long. Here's just a very short snippet: There was a problem sending 341 bytes on socket 17: Broken pipeThere was a problem sending 340 bytes on socket 17: Broken pipeThere was a problem sending 341 bytes on socket 17: Broken pipeThere was a problem sending 341 bytes on socket 17: Broken pipeThere was a problem sending 340 bytes on socket 17: Broken pipeThere was a problem sending 341 bytes on socket 17: Broken pipeThere was a problem sending 341 bytes on socket 17: Broken pipeThere was a problem sending 340 bytes on socket 17: Broken pipeThere was a problem sending 341 bytes on socket 17: Broken pipeThere was a problem sending 341 bytes on socket 17: Broken pipeThere was a problem sending 340 bytes on socket 17: Broken pipeThere was a problem sending 341 bytes on socket 17: Broken pipeThere was a problem sending 341 bytes on socket 17: Broken pipeThere was a problem sending 342 bytes on socket 17: Broken pipeThere was a problem sending 335 bytes on socket 17: Broken pipeThere was a problem sending 340 bytes on socket 17: Broken pipeThere was a problem sending 340 bytes on socket 17: Broken pipeThere was a problem sending 355 bytes on socket 17: Broken pipeThere was a problem sending 367 bytes on socket 17: Broken pipeThere was a problem sending 364 bytes on socket 17: Broken pipeThere was a problem sending 366 bytes on socket 17: Broken pipeThere was a problem sending 360 bytes on socket 17: Broken pipeThere was a problem sending 360 bytes on socket 17: Broken pipeThere was a problem sending 359 bytes on socket 17: Broken pipeThere was a problem sending 362 bytes on socket 17: Broken pipeThere was a problem sending 358 bytes on socket 17: Broken pipeThere was a problem sending 358 bytes on socket 17: Broken pipeThere was a problem sending 369 bytes on socket 17: Broken pipeThere was a problem sending 357 bytes on socket 17: Broken pipeThere was a problem sending 340 bytes on socket 17: Broken pipeThere was a problem sending 340 bytes on socket 17: Broken pipeThere was a problem sending 338 bytes on socket 17: Broken pipeThere was a problem sending 338 bytes on socket 17: Broken pipeThere was a problem sending 342 bytes on socket 17: Broken pipeThere was a problem sending 338 bytes on socket 17: Broken pipeThere was a problem sending 342 bytes on socket 17: Broken pipeThere was a problem sending 338 bytes on socket 17: Broken pipeThere was a problem sending 342 bytes on socket 17: Broken pipeThere was a problem sending 338 bytes on socket 17: Broken pipeThere was a problem sending 342 bytes on socket 17: Broken pipeThere was a problem sending 338 bytes on socket 17: Broken pipeThere was a problem sending 342 bytes on socket 17: Broken pipeThere was a problem sending 346 bytes on socket 17: Broken pipeThere was a problem sending 334 bytes on socket 17: Broken pipe
Steps To Reproduce	Somehow break PhPStorm in a way that xdebug really keeps trying to send it data while debugging.
Tags	No tags attached.

Operating System	MacOS 10.14.3
PHP Version	7.1.25-7.1.29

derick 2019-03-10 17:17 administrator ~0004955	I've made a pull request to address the missing new line (and add the Unix timestamp to the beginning): https://github.com/derickr/xdebug/tree/issue1646-socket-warning I'm curious to hear whether you can find a way on how to reproduce this though.

dwilks 2019-03-14 22:57 reporter ~0004970	https://youtrack.jetbrains.com/issue/WI-45825 for the repro case. Basically just hit their debugger's stop button while a script is executing.

derick 2019-03-21 14:13 administrator ~0004975	Hi, I can now reproduce this. I'll go have a look at whether I can fix this. cheers, Derick

derick 2019-04-05 10:48 administrator ~0004983	There was indeed a bug here, which I've fixed for Xdebug 2.7.1 (soon to be released).

View Issue Details

Activities