Description:
5.7-m15:

==== 
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 
etc. 

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

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 ;-)?)

++1

+1!

a subset of this would be:
http://bugs.mysql.com/bug.php?id=1694
http://bugs.mysql.com/bug.php?id=35661
http://bugs.mysql.com/bug.php?id=55594

+1

+1

Hello Roel,

Thank you for the feature request.

Thanks,
Umesh

I agree that this would be useful enhancement.