Bug #56648 mtr does not print stack trace for all crashes
Submitted: 8 Sep 2010 13:55 Modified: 10 Feb 2011 14:41
Reporter: Sven Sandberg Email Updates:
Status: Closed Impact on me:
None 
Category:Tools: MTR / mysql-test-run Severity:S7 (Test Cases)
Version:5.1 OS:Any
Assigned to: Bjørn Munch CPU Architecture:Any
Tags: mtr

[8 Sep 2010 13:55] Sven Sandberg
Description:
The server crashes and mysqltest/mtr/pb2 does not produce any debug info, many times, in trunk-bugfixing in pb2 at https://central.sun.net/http://pb2.norway.sun.com/?action=archive_download&archive_id=2239... :

Symptom 1:
Server [mysqld.1 - pid: 14230, winpid: 14230, exit: 256] failed during test run

Symptom 2:
The server [mysqld.1 - pid: 14661, winpid: 14661, exit: 256] crashed while running 'check testcase before test'

Symptom 3:
Failed to start mysqld.3

Symptom 4:
mysqltest: At line 11: query 'call mtr.check_testcase()' failed: 2013: Lost connection to MySQL server during query

There are several occurrences of the above lines or variations of them. The lines say that the server crashed, but they don't say anything else. This looks like a severe problem, but it's impossible to even start investigating it before we can get a stack trace.

How to repeat:
Read the log.

Suggested fix:
Make mysqltest/mtr/pb2 print something useful, like a stack trace, for these crashes.
[8 Sep 2010 14:26] Bjørn Munch
I don't quite understand what you're asking. If the server has crashed, unless it has produced a core file, there's no way to get a stack trace from it.
[8 Oct 2010 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".