Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1(EOL)
-
None
Description
See
http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/26/steps/test/logs/stdio
http://buildbot.askmonty.org/buildbot/builders/winx64-packages/builds/88/steps/test/logs/stdio
***Warnings generated in error logs during shutdown after running tests: main.shm
|
|
|
160502 9:49:14 [ERROR] mysqld got exception 0xc0000005 ;
|
Attempting backtrace. You can use the following information to find out
|
The problem isn't new, we had it mentioned in MDEV-9151. That JIRA item is not about the crash itself, only about MTR not printing the stack trace. The request is valid, but even printing the stack trace wouldn't help much in this case, see the error log:
2016-05-02 10:04:37 7480 [Note] D:/winx64-packages/build/sql//RelWithDebInfo/mysqld.exe: ready for connections.
|
Version: '10.1.13-MariaDB' socket: '' port: 16140 mariadb.org binary distribution
|
2016-05-02 10:04:39 6040 [Note] D:/winx64-packages/build/sql//RelWithDebInfo/mysqld.exe: Normal shutdown
|
|
|
2016-05-02 10:04:39 6040 [Note] D:/winx64-packages/build/sql//RelWithDebInfo/mysqld.exe: Shutdown complete
|
|
|
160502 10:04:39 [ERROR] mysqld got exception 0xc0000005 ;
|
This could be because you hit a bug. It is also possible that this binary
|
or one of the libraries it was linked against is corrupt, improperly built,
|
or misconfigured. This error can also be caused by malfunctioning hardware.
|
|
|
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
|
|
|
We will try our best to scrape up some info that will hopefully help
|
diagnose the problem, but since we have already crashed,
|
something is definitely wrong and this may fail.
|
|
|
Server version: 10.1.13-MariaDB
|
read_buffer_size=131072
|
max_used_connections=2
|
thread_count=0
|
Thread pointer: 0x0x1112016788
|
Attempting backtrace. You can use the following information to find out
|
where mysqld died. If you see no messages after this, something went
|
terribly wrong...
|
Got exception in exception handler!
|
Attachments
Issue Links
- blocks
-
MDEV-7069 Fix buildbot failures in main server trees
-
- Stalled
-