6. 数据库插入
插入操作前，切换schema和查询都是没问题的：
mysql> use gdb Database changed mysql> show tables; +---------------+ | Tables_in_gdb | +---------------+ | test | +---------------+ 1 row in set (0.00 sec) mysql> select * from test; +------+ | id | +------+ | 1 | | 2 | +------+ 2 rows in set (0.00 sec)
插入一条 id=3 的数据，出现了等待：
mysql> insert into test values (3);
7. 分析断点信息
断点触发，如下：
(gdb) c Continuing. [Switching to Thread 0x2b15faf02700 (LWP 21617)] Breakpoint 1, Sql_cmd_insert::mysql_insert (this=0x2b1614008348, thd=0x2b1614003af0, table_list=0x2b1614007db8) at /gdb/mysql-5.7.25/sql/sql_insert.cc:423 423 DBUG_ENTER("mysql_insert");
bt 命令展示栈帧：
(gdb) bt #0 Sql_cmd_insert::mysql_insert (this=0x2b1614008348, thd=0x2b1614003af0, table_list=0x2b1614007db8) at /gdb/mysql-5.7.25/sql/sql_insert.cc:423 #1 0x000000000176256e in Sql_cmd_insert::execute (this=0x2b1614008348, thd=0x2b1614003af0) at /gdb/mysql-5.7.25/sql/sql_insert.cc:3118 #2 0x000000000153b093 in mysql_execute_command (thd=0x2b1614003af0, first_level=true) at /gdb/mysql-5.7.25/sql/sql_parse.cc:3596 #3 0x0000000001540820 in mysql_parse (thd=0x2b1614003af0, parser_state=0x2b15faf01690) at /gdb/mysql-5.7.25/sql/sql_parse.cc:5570 #4 0x0000000001536131 in dispatch_command (thd=0x2b1614003af0, com_data=0x2b15faf01df0, command=COM_QUERY) at /gdb/mysql-5.7.25/sql/sql_parse.cc:1484 #5 0x0000000001534f9a in do_command (thd=0x2b1614003af0) at /gdb/mysql-5.7.25/sql/sql_parse.cc:1025 #6 0x00000000016658dc in handle_connection (arg=0x39610f0) at /gdb/mysql-5.7.25/sql/conn_handler/connection_handler_per_thread.cc:306 #7 0x0000000001ced592 in pfs_spawn_thread (arg=0x5508e50) at /gdb/mysql-5.7.25/storage/perfschema/pfs.cc:2190 #8 0x00002b15cd699e25 in start_thread () from /lib64/libpthread.so.0 #9 0x00002b15ce80ebad in clone () from /lib64/libc.so.6
接下来输入 n 会逐行输出，我们这里直接 continue，阻塞的 insert 也完成了：
mysql> insert into test values (3); Query OK, 1 row affected (2 min 49.57 sec)
发布一个特殊版本的mysql
有些函数所在源码的位置比较好理解，比如上面的 insert 功能，或者 delete 功能。是不是可以通过修改 delete 函数，打包一个数据永不会被删除的 mysql 呢？
定位函数位置
先追踪mysql进程：
(gdb) attach 21357 Attaching to process 21357 Reading symbols from /gdb/mysql/bin/mysqld...done. Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. [New LWP 5584] [New LWP 5583] [New LWP 21617] [New LWP 21387] [New LWP 21386] [New LWP 21384] [New LWP 21383] [New LWP 21382] [New LWP 21381] [New LWP 21380] [New LWP 21379] [New LWP 21378] [New LWP 21377] [New LWP 21376] [New LWP 21375] [New LWP 21374] [New LWP 21373] [New LWP 21369] [New LWP 21368] [New LWP 21367] [New LWP 21366] [New LWP 21365] [New LWP 21364] [New LWP 21363] [New LWP 21362] [New LWP 21361] [New LWP 21360] [New LWP 21359] [New LWP 21358] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libcrypt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libcrypt.so.1 Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/librt.so.1 Reading symbols from /lib64/libstdc++.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libstdc++.so.6 Reading symbols from /lib64/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libm.so.6 Reading symbols from /lib64/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libgcc_s.so.1 Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libfreebl3.so...Reading symbols from /lib64/libfreebl3.so...(no debugging symbols found)...done. (no debugging symbols found)...done. Loaded symbols for /lib64/libfreebl3.so Reading symbols from /lib64/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libnss_files.so.2 Reading symbols from /lib64/libnss_sss.so.2...Reading symbols from /lib64/libnss_sss.so.2...(no debugging symbols found)...done. (no debugging symbols found)...done. Loaded symbols for /lib64/libnss_sss.so.2 0x00002b15ce803f0d in poll () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install glibc-2.17-222.el7.x86_64 libgcc-4.8.5-39.el7.x86_64 libstdc++-4.8.5-39.el7.x86_64 nss-softokn-freebl-3.34.0-2.el7.x86_64 sssd-client-1.16.0-19.el7.x86_64
delete函数这里打上断点：
(gdb) b Sql_cmd_delete::mysql_delete Breakpoint 1 at 0x175198b: file /gdb/mysql-5.7.25/sql/sql_delete.cc, line 50.
数据库执行delete语句触发断点：
mysql> delete from test where id =3;
gbk断点信息：
Breakpoint 1, Sql_cmd_delete::mysql_delete (this=0x2b16040020c8, thd=0x2b1604007e30, limit=18446744073709551615) at /gdb/mysql-5.7.25/sql/sql_delete.cc:50 50 DBUG_ENTER("mysql_delete");
查看相关栈帧：
#0 Sql_cmd_delete::mysql_delete (this=0x2b16040020c8, thd=0x2b1604007e30, limit=18446744073709551615) at /gdb/mysql-5.7.25/sql/sql_delete.cc:50 #1 0x0000000001755cc6 in Sql_cmd_delete::execute (this=0x2b16040020c8, thd=0x2b1604007e30) at /gdb/mysql-5.7.25/sql/sql_delete.cc:1392 #2 0x000000000153b12f in mysql_execute_command (thd=0x2b1604007e30, first_level=true) at /gdb/mysql-5.7.25/sql/sql_parse.cc:3606 #3 0x0000000001540820 in mysql_parse (thd=0x2b1604007e30, parser_state=0x2b15faf43690) at /gdb/mysql-5.7.25/sql/sql_parse.cc:5570 #4 0x0000000001536131 in dispatch_command (thd=0x2b1604007e30, com_data=0x2b15faf43df0, command=COM_QUERY) at /gdb/mysql-5.7.25/sql/sql_parse.cc:1484 #5 0x0000000001534f9a in do_command (thd=0x2b1604007e30) at /gdb/mysql-5.7.25/sql/sql_parse.cc:1025 #6 0x00000000016658dc in handle_connection (arg=0x54b6510) at /gdb/mysql-5.7.25/sql/conn_handler/connection_handler_per_thread.cc:306 #7 0x0000000001ced592 in pfs_spawn_thread (arg=0x5508e50) at /gdb/mysql-5.7.25/storage/perfschema/pfs.cc:2190 #8 0x00002b15cd699e25 in start_thread () from /lib64/libpthread.so.0 #9 0x00002b15ce80ebad in clone () from /lib64/libc.so.6
修改源码
可以看到 #1 是 Sql_cmd_delete::execute ，这个就是 delete 处理的函数，去源代码中找到相应函数：
把正真实现删除逻辑的代码给注释掉，返回的 res 值直接赋成 true：
boolSql_cmd_delete::execute(THD *thd){DBUG_ASSERT(thd->lex->sql_command == SQLCOM_DELETE);LEX *const lex= thd->lex;SELECT_LEX *const select_lex= lex->select_lex;SELECT_LEX_UNIT *const unit= lex->unit;TABLE_LIST *const first_table= select_lex->get_table_list();TABLE_LIST *const all_tables= first_table;if(delete_precheck(thd, all_tables))returntrue;DBUG_ASSERT(select_lex->offset_limit ==0);unit->set_limit(select_lex);/* Push ignore / strict error handler */Ignore_error_handler ignore_handler;Strict_error_handler strict_handler;if(thd->lex->is_ignore())thd->push_internal_handler(&ignore_handler);elseif(thd->is_strict_mode())thd->push_internal_handler(&strict_handler);/*注释以下删除逻辑的代码*//*MYSQL_DELETE_START(const_cast<char*>(thd->query().str));bool res = mysql_delete(thd, unit->select_limit_cnt);MYSQL_DELETE_DONE(res, (ulong) thd->get_row_count_func());*//*直接返回true*/bool res =true;/* Pop ignore / strict error handler */if(thd->lex->is_ignore()|| thd->is_strict_mode())thd->pop_internal_handler();return res;}
然后上文的方法去重新编译mysql，启动后就会发现delete语句无法删除数据了。
调试总结
如果想深入学习源码，就可以从栈帧出发，但是这是基于知道函数接口功能的前提下进行的，如果不知道某个功能会调用什么函数，断点调试就很难进行了。
直接去读完 mysql 所有源码，成本太高，而且 mysql 的代码结构并不友好，耗时耗力不值得。最好的方案还是遇到问题时或针对特殊的一个功能点按需去寻找函数入口，然后逐步深入分析。
希望这篇文章可以帮到想接触mysql源码调试的同学，以后我遇到特殊的问题也会通过gdb去调试涉及的相关函数，大家可以持续关注~
全文完。
Enjoy MySQL :)
