Bug #56400 please assert instead of calling exit(1)
Submitted: 31 Aug 2010 8:10 Modified: 11 Mar 2013 20:02
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S4 (Feature request)
Version:5.1, 5.5 OS:Any
Assigned to: CPU Architecture:Any

[31 Aug 2010 8:10] Shane Bester
in many cases innodb calls exit(1) when it hits a fatal error.
this is a feature request to assert instead.  then we may get a crash dump and more information about the current process state.  also, the windows event viewer will have an entry for a crashed process, but not when a normal exit(1) call is made.

How to repeat:
grep the innodb source for exit(1)

Suggested fix:
trigger an assertion instead of exit(1)
[11 Mar 2013 20:02] Bugs System
Added 5.7.2 changelog.

In many cases InnoDB calls exit(1) when it encounters a fatal error. An exit(1) call does not cause a crash dump or provide information about the process state. Additionally, on Windows, an exit(1) call does not report a crashed processes in the Event Viewer. This fix replaces exit(1) calls with ut_error calls in a number of places.