Incorrect time zone parsing reads garbage in memory [CORE6046] #6296
Assignees
Comments
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Beta 2 [ 10888 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Deferred Test Details: Any example with concrete data (which led to garbage) will be appreciated. |
|
Commented by: @asfernandes No way to consistently reproduce, as it was reading invalid memory locations. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Deferred => Cannot be tested Test Details: Any example with concrete data (which led to garbage) will be appreciated. => |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @asfernandes
Sometimes running TCS tests some errors appears:
Invalid time zone region: America/Los_Angeles0
or
Invalid time zone region: America/Los_Angeles1
Some garbage character may be read after the string bounds.
Commits: 5ca2d86 158ee4a
The text was updated successfully, but these errors were encountered: