Bug #75536 5.7: improved crash reporting?
Submitted: 17 Jan 2015 3:47 Modified: 19 Jan 2015 9:29
Reporter: Roel Van de Paar Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Logging Severity:S4 (Feature request)
Version: OS:Any
Assigned to: CPU Architecture:Any

[17 Jan 2015 3:47] Roel Van de Paar

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68117 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Could we please have much improved crash reporting in 5.7 please?

- Plugins/Modules in use
- Accurate memory calculations
- Resolved stack traces with/without variables 
- Full stack traces of all threads
- All queries running at the time of the crash, in all threads
- Values of variables 

Are just a few ideas for much improved crash reports. 

This would do EVERYONE a favor: developers will find it easier to fix bugs found, customers will have faster resolution and more info to provide etc.

Maybe the data can even be written to a seperate file, and the error log could state "See {assert_xyz_PID.log}" 

How to repeat:
Crash/assert mysqld
[17 Jan 2015 3:49] Roel Van de Paar
Seperate file would be great (as it does not clutter log). Also include locks, innodb status etc. etc. (Why did we not do this before yet ;-)?)
[17 Jan 2015 3:54] Ramesh Sivaraman
[17 Jan 2015 3:55] George Lorch
[17 Jan 2015 4:42] MySQL Verification Team
a subset of this would be:
[17 Jan 2015 7:33] Valeriy Kravchuk
[17 Jan 2015 10:29] Tomislav Plavcic
[19 Jan 2015 9:29] MySQL Verification Team
Hello Roel,

Thank you for the feature request.

[19 Jan 2015 14:50] Joel Epstein
I agree that this would be useful enhancement.