| Bug #86358 | data node doesn't generate core files on windows | ||
|---|---|---|---|
| Submitted: | 17 May 2017 14:51 | ||
| Reporter: | Mikiya Okuno | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
| Version: | 7.5.6 | OS: | Windows |
| Assigned to: | CPU Architecture: | Any | |
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.042 sec. using MySQL 8.0.36-u4-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
© 2024, Oracle Corporation and/or its affiliates
Description: According to definition of childAbort() function, no special handling isn't performed on Windows; the process just exits with exit code 255: static void childAbort(int error_code, int exit_code, Uint32 currentStartPhase) { writeChildInfo("error", error_code); writeChildInfo("sphase", currentStartPhase); fprintf(angel_info_w, "\n"); fclose(angel_info_w); #ifdef _WIN32 // Don't use 'abort' on Windows since it returns // exit code 3 which conflict with NRT_NoStart_InitialStart ndbd_exit(exit_code); #else signal(SIGABRT, SIG_DFL); abort(); #endif } How to repeat: Enable --core-file option on Windows, then crash the data node. Suggested fix: Call MiniDumpWriteDump() function just like what my_create_minidump() function in mysys/stacktrace.c does.