File: log_backtrace_debug.result

package info (click to toggle)
mysql-8.0 8.0.43-3
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 1,273,924 kB
  • sloc: cpp: 4,684,605; ansic: 412,450; pascal: 108,398; java: 83,641; perl: 30,221; cs: 27,067; sql: 26,594; sh: 24,181; python: 21,816; yacc: 17,169; php: 11,522; xml: 7,388; javascript: 7,076; makefile: 2,194; lex: 1,075; awk: 670; asm: 520; objc: 183; ruby: 97; lisp: 86
file content (61 lines) | stat: -rw-r--r-- 1,994 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
# WL14955: Have backtraces of failed runs appear in pfs.error_log
#

#
# Take down server started by mtr.
#
# Start our own server. Log to LOG_FILE1.
#
# Connect to our own server.
#
# Log a header.
# If the header is present, but the stackdump is not, the stackdump
# failed. If the header is not present, we have bigger issues.
SET @@session.debug="+d,parser_stmt_to_error_log_with_system_prio";
SELECT "--- STACKTRACE TO FOLLOW ---";
--- STACKTRACE TO FOLLOW ---
--- STACKTRACE TO FOLLOW ---
SET @@session.debug="-d,parser_stmt_to_error_log_with_system_prio";
#
# Let's synthesize a crash, so to hopefully get a backtrace.
SET @@session.debug='d,crash_now';
ERROR HY000: Lost connection to MySQL server during query
#
# Restart mysqld after the crash using the same log-file.
# Then, reconnect.
# restart: --log-error=LOG_FILE1 --log-timestamps=UTC
#
# Connect to our own server.
#
# Check error-log file for stacktrace.
# Test 1: expect one match (processed line only)
include/assert_grep.inc [Found the expected stacktrace in the error-log file.]
#
# Check error-log file for stacktrace.
# Test 2: expect two matches (original and processed line)
include/assert_grep.inc [Found the expected stacktraces in the error-log file.]
#
# Show that a stacktrace was created, and was read at start-up.
# While in log_backtrace.test, we wrote the processed stacktrace
# to the JSON-log, this time we'll use the traditional error-log
# format. It is worth testing both scenarios (input and output in
# different log files vis-a-vis input and output in the same log
# file).
SET @err_code=ER_STACK_BACKTRACE;
#
# Look for 'SELECT'-header.
SELECT data
FROM performance_schema.error_log
WHERE data LIKE "%--- STACKTRACE TO FOLLOW ---%";
data
Parser saw: SELECT "--- STACKTRACE TO FOLLOW ---"
#
# Look for stacktrace in pfs.error_log. Should find 1 signal-header.
SELECT COUNT(*)
FROM performance_schema.error_log
WHERE error_code=@err_code
AND data LIKE "% UTC - mysqld got %";
COUNT(*)
1
#
# Clean up.