Bug #81651 Newline issue for "Query (0):" in error log on crash
Submitted: 31 May 2016 1:10 Modified: 21 Jun 2016 8:47
Reporter: Roel Van de Paar Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Logging Severity:S4 (Feature request)
Version:5.7.12, 5.6.31 OS:Any
Assigned to: CPU Architecture:Any

[31 May 2016 1:10] Roel Van de Paar
Description:
For crash stack reporting by mysqld in the error log, we can see;

Query (0): Connection ID (thread ID): 8

When no query is found, whereas it shows;

Query (7fdfe0008e50): set global innodb_file_format_max=default
Connection ID (thread ID): 7

When a query is found.

How to repeat:
Seen in error log from crash stack reporting by mysqld.

Suggested fix:
Insert newline after Query (...): ... even if no query was found.
[31 May 2016 1:11] Roel Van de Paar
Note to pquery-prep-red.sh users; this causes the following to be added to pquery SQL traces; 

Connection ID (thread ID): 8; ;
Connection ID (thread ID): 8; ;
Connection ID (thread ID): 8; ;

When no query was found in the mysqld error log.
[31 May 2016 1:12] Roel Van de Paar
This is likely a 5.7 issue only, as I did not see this before.
[21 Jun 2016 8:47] MySQL Verification Team
Hello Roel,

Thank you for the feature request.
I've seen recently similar issue(Bug#81033) with 5.6.31 build.

-- 5.6.31

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 1
Status: KILL_CONNECTION

Thanks,
Umesh