Issues
2 of 2
LP #888113: MySQLProtocolParser crashes on some prepared statements
Incomplete
General
Escalation
General
Escalation
Description
Environment
None
Smart Checklist
Details
Assignee
UnassignedUnassignedReporter
lpjirasynclpjirasync(Deactivated)Priority
Low
Details
Details
Assignee
Unassigned
UnassignedReporter
lpjirasync
lpjirasync(Deactivated)Priority
Smart Checklist
Smart Checklist
Smart Checklist
Created January 24, 2018 at 6:05 PM
Updated April 2, 2024 at 4:13 PM
Resolved April 2, 2024 at 4:13 PM
Activity
Show:
Sveta SmirnovaApril 2, 2024 at 4:13 PM
There is no test case, so won't fix this until we know how to repeat it.
lpjirasyncJanuary 24, 2018 at 6:05 PM
**Comment from Launchpad by: Daniel Nichter on: 31-05-2012 13:52:37
Huadaonan, why did you change this to Fix Released?
**Reported in Launchpad by Daniel Nichter last update 24-02-2014 20:56:45
Pipeline process 3 (MySQLProtocolParser) caused an error: Argument "" isn't numeric in substr at ./pt-query-digest line 3410, <> line 1304.