VM stack traces can include blank lines

[nex3]

I'm not sure how to reproduce this, but comment 12 on issue #9 ( contains an example from a user of a stack trace with a blank line (between #­6 and #­7). This is unhelpful for users and causes problems with the stack_trace package.

[nex3]

The stack_trace package now includes a workaround for this.

[iposva-google]

Set owner to @zanderso.
Removed Priority-Unassigned label.
Added Priority-Medium, Accepted labels.

[zanderso]

Looking at Stacktrace::ToCStringInternal(), since all of the constant and format strings end with newlines only after non-zero characters are printed, it appears to me to be impossible that the blank line in the above mentioned stack trace was generated there.

[nex3]

It's possible I'm misreading the output, but it certainly looks like a blank line. Have you tried reproducing it against 1.1.0-dev.5.0 using the steps outlined in issue #15709?

[zanderso]

My guess would be that the blank line is the tail end of the output "Connection closed before full header was received", and that the error message "Couldn't parse VM stack trace line 'null'" refers literally to a string reading 'null', rather than to an empty string, which would have yielded the error message "Couldn't parse VM stack trace line ''" if I am reading the source correctly.

[nex3]

This is very puzzling. I've tried to reproduce this with the literal stack trace string from issue #15709, but the error message is different: "Couldn't parse VM stack trace line ''." Looking through the code I can't see where a null value or a literal null string would be appearing.

Since issue #15709 doesn't seem to be reproducing anymore (nor can I reproduce it against 1.1.0-dev.5.0), I'm going to close this out. I'll re-open if I see this again and can track it down further.

---

Added CannotReproduce label.