iovisor / iovisor/bcc

why not trace mysql function

Open
#1,640 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
22.7k
Forks
4.1k
Avg merge
10d 4h
Merged PRs (30d)
3

Description

[root@hadoop03 tools]# ./trace -U -p 26720 '/usr/local/mysql/bin/mysqld:log_buffer_flush_to_disk'
could not determine address of symbol log_buffer_flush_to_disk

[root@hadoop03 ~]# objdump -t /usr/local/mysql/bin/mysqld|grep -i log_buffer_flush_to_disk
00000000019523a5 g F .text 0000000000000057 _Z24log_buffer_flush_to_diskb

[root@hadoop03 ~]# gdb -p 26720
...
(gdb) b log_buffer_flush_to_disk
Breakpoint 1 at 0x19523b3: file /root/mysql-5.7.21/storage/innobase/log/log0log.cc, line 1417.

[root@hadoop03 tools]# uname -sr
Linux 4.15.9-1.el7.elrepo.x86_64

Is there a problem with my usage?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the ./trace command against /usr/local/mysql/bin/mysqld:log_buffer_flush_to_disk and compare its symbol lookup with the objdump and gdb results shown. Read the trace tool's symbol-resolution entry point and verify whether the mangled _Z24log_buffer_flush_to_diskb symbol is handled; done means explaining the failure or confirming a usage or tool defect.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux, mysql
Domain
observability, operating-systems, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.