[mysqldumpslow 报错] Died at /usr/local/mysql/bin/mysqldumpslow line 161, chunk 236. mysqldumpslow报错: Died at /usr/local/mysql/bin/mysqldumpslow line 161, chunk 236. 总结:是因为top数目太多了,mysqldumpslow遍历不过来的缘故。 /usr/local/m
[mysqldumpslow 报错] Died at /usr/local/mysql/bin/mysqldumpslow line 161, chunk 236.mysqldumpslow报错:Died at /usr/local/mysql/bin/mysqldumpslow line 161, chunk 236.
总结:是因为top数目太多了,mysqldumpslow遍历不过来的缘故。
/usr/local/mysql/bin/mysqldumpslow -s -t 15 /root/db01-102-slow.log
1,把r去掉试试,还是报错,参数不识别。
[root@slave ]# /usr/local/mysql/bin/mysqldumpslow -s -t 15 /root/db01-102-slow.log Reading mysql slow query log from 15 /root/db01-102-slow.log Can't open 15: 没有那个文件或目录 at /usr/local/mysql/bin/mysqldumpslow line 91. Count: 22 Time=9.61s (211s) Lock=0.00s (0s) Rows=1.0 (22), [dubbo]@2hosts select count(*) from coupon_lot left join coupon on coupon.coupon_lot_id = coupon_lot.coupon_lot_id LEFT JOIN brand ON brand.brand_id=coupon_lot.brand_id LEFT JOIN product_category on product_category.category_id=coupon_lot.category_id Count: 177 Time=1.40s (247s) Lock=0.00s (0s) Rows=1.0 (177), [dubbo]@2hosts select count(*) from user_info LEFT JOIN system_region a ON province_id =a.region_id LEFT JOIN system_region b ON city_id = b.region_id LEFT JOIN system_region c ON district_id = c.region_id Count: 22 Time=13.20s (290s) Lock=0.00s (0s) Rows=10.0 (220), [dubbo]@2hosts select coupon_id, coupon_lot.coupon_lot_id, coupon_lot.remark, coupon.code, coupon_lot.coupon_type, coupon.state, coupon_lot.ckey, coupon_lot.cvalue, coupon_lot.discount, coupon_lot.type, coupon_lot.channel, coupon_lot.is_reusable, coupon_lot.start_datetime, coupon_lot.end_datetime, coupon_lot.create_datetime, coupon.update_datetime ,coupon_lot.department, coupon_lot.state as couponLotState, coupon_lot.create_operator,coupon_lot.coupon_category, coupon_lot.pdt_code,brand.brand_name,product_category.category_name from coupon_lot left join coupon on coupon.coupon_lot_id = coupon_lot.coupon_lot_id LEFT JOIN brand ON brand.brand_id=coupon_lot.brand_id LEFT JOIN product_category on product_category.category_id=coupon_lot.category_id group by coupon_lot.coupon_lot_id order by coupon_lot.create_datetime DESC limit N,N Count: 8 Time=1.09s (8s) Lock=0.00s (0s) Rows=10.0 (80), [dubbo]@2hosts select return_sn, relating_order_sn, return_from, oi.order_out_sn , add_time , return_type, return_pay, ui.usename as userName, return_consignee, return_goods_count , return_total_fee, total_paid, return_desc, return_order_status, return_pay_status , return_shipping_status, order_return.lock_operator, order_return.return_invoice_no from order_return LEFT JOIN order_info oi on order_return.relating_order_sn = oi.order_sn left join user_info ui on oi.user_id = ui.user_id left join order_payment on order_payment.order_sn = oi.order_sn order by order_return.add_time DESC limit N,N Count: 1 Time=1.00s (1s) Lock=0.00s (0s) Rows=1.0 (1), root[root]@localhost select sleep(N) Count: 1 Time=1.13s (1s) Lock=0.00s (0s) Rows=10.0 (10), [dubbo]@[xx] select return_sn, relating_order_sn, return_from, oi.order_out_sn , add_time , return_type, return_pay, ui.usename as userName, return_consignee, return_goods_count , return_total_fee, total_paid, return_desc, return_order_status, return_pay_status , return_shipping_status, order_return.lock_operator, order_return.return_invoice_no from order_return LEFT JOIN order_info oi on order_return.relating_order_sn = oi.order_sn left join user_info ui on oi.user_id = ui.user_id left join order_payment on order_payment.order_sn = oi.order_sn order by order_return.add_time DESC , oi.order_sn limit N,N Count: 5 Time=2.47s (12s) Lock=0.00s (0s) Rows=0.0 (0), [dubbo]@2hosts select user_id, usename, nickname, password, user_group_id, realname, gender, email, mobilephone, birthday, province_id, city_id, district_id, marry, income, remarks, create_datetime, active_state, verityEmail, verityPhone, credit, last_login, last_ip, is_locked, channel, tag, union_partner_uuid, union_user_safekey, is_black, qq, weibo_id, verity_email_key, verity_phone_key, verity_email_datetime, verity_phone_datetime, verity_question, verity_answer, cps_code, cps_time_from, cps_time_to, cps_cookie, first_channel from user_info where mobilephone = 'S' and (channel is null or trim(channel) ='S')
2,查看下mysqldumpslow 使用参数,-s后面需要带参数的,看了西夏at比较合适
[root@db-master-2 ~]# /usr/local/mysql/bin/mysqldumpslow --help Usage: mysqldumpslow [ OPTS... ] [ LOGS... ] Parse and summarize the MySQL slow query log. Options are --verbose verbose --debug debug --help write this text to standard output -v verbose -d debug -s ORDER what to sort by (al, at, ar, c, l, r, t), 'at' is default al: average lock time ar: average rows sent at: average query time c: count l: lock time r: rows sent t: query time -r reverse the sort order (largest last instead of first) -t NUM just show the top n queries -a don't abstract all numbers to N and strings to 'S' -n NUM abstract numbers with at least n digits within names -g PATTERN grep: only consider stmts that include this string -h HOSTNAME hostname of db server for *-slow.log filename (can be wildcard), default is '*', i.e. match all -i NAME name of server instance (if using mysql.server startup script) -l don't subtract lock time from total time
[root@db-master-2 ~]# /usr/local/mysql/bin/mysqldumpslow -s at -t 15 /root/db01-102-slow.log Reading mysql slow query log from /root/db01-102-slow.log Count: 22 Time=13.20s (290s) Lock=0.00s (0s) Rows=10.0 (220), [dubbo]@2hosts select coupon_id, coupon_lot.coupon_lot_id, coupon_lot.remark, coupon.code, coupon_lot.coupon_type, coupon.state, coupon_lot.ckey, coupon_lot.cvalue, coupon_lot.discount, coupon_lot.type, coupon_lot.channel, coupon_lot.is_reusable, coupon_lot.start_datetime, coupon_lot.end_datetime, coupon_lot.create_datetime, coupon.update_datetime ,coupon_lot.department, coupon_lot.state as couponLotState, coupon_lot.create_operator,coupon_lot.coupon_category, coupon_lot.pdt_code,brand.brand_name,product_category.category_name from coupon_lot left join coupon on coupon.coupon_lot_id = coupon_lot.coupon_lot_id LEFT JOIN brand ON brand.brand_id=coupon_lot.brand_id LEFT JOIN product_category on product_category.category_id=coupon_lot.category_id group by coupon_lot.coupon_lot_id order by coupon_lot.create_datetime DESC limit N,N Count: 22 Time=9.61s (211s) Lock=0.00s (0s) Rows=1.0 (22), [dubbo]@2hosts select count(*) from coupon_lot left join coupon on coupon.coupon_lot_id = coupon_lot.coupon_lot_id LEFT JOIN brand ON brand.brand_id=coupon_lot.brand_id LEFT JOIN product_category on product_category.category_id=coupon_lot.category_id Count: 5 Time=2.47s (12s) Lock=0.00s (0s) Rows=0.0 (0), [dubbo]@2hosts select user_id, usename, nickname, password, user_group_id, realname, gender, email, mobilephone, birthday, province_id, city_id, district_id, marry, income, remarks, create_datetime, active_state, verityEmail, verityPhone, credit, last_login, last_ip, is_locked, channel, tag, union_partner_uuid, union_user_safekey, is_black, qq, weibo_id, verity_email_key, verity_phone_key, verity_email_datetime, verity_phone_datetime, verity_question, verity_answer, cps_code, cps_time_from, cps_time_to, cps_cookie, first_channel from user_info where mobilephone = 'S' and (channel is null or trim(channel) ='S') Count: 177 Time=1.40s (247s) Lock=0.00s (0s) Rows=1.0 (177), [dubbo]@2hosts select count(*) from user_info LEFT JOIN system_region a ON province_id =a.region_id LEFT JOIN system_region b ON city_id = b.region_id LEFT JOIN system_region c ON district_id = c.region_id Count: 1 Time=1.13s (1s) Lock=0.00s (0s) Rows=10.0 (10), [dubbo]@[10.10.3.8] select return_sn, relating_order_sn, return_from, oi.order_out_sn , add_time , return_type, return_pay, ui.usename as userName, return_consignee, return_goods_count , return_total_fee, total_paid, return_desc, return_order_status, return_pay_status , return_shipping_status, order_return.lock_operator, order_return.return_invoice_no from order_return LEFT JOIN order_info oi on order_return.relating_order_sn = oi.order_sn left join user_info ui on oi.user_id = ui.user_id left join order_payment on order_payment.order_sn = oi.order_sn order by order_return.add_time DESC , oi.order_sn limit N,N Count: 8 Time=1.09s (8s) Lock=0.00s (0s) Rows=10.0 (80), [dubbo]@2hosts select return_sn, relating_order_sn, return_from, oi.order_out_sn , add_time , return_type, return_pay, ui.usename as userName, return_consignee, return_goods_count , return_total_fee, total_paid, return_desc, return_order_status, return_pay_status , return_shipping_status, order_return.lock_operator, order_return.return_invoice_no from order_return LEFT JOIN order_info oi on order_return.relating_order_sn = oi.order_sn left join user_info ui on oi.user_id = ui.user_id left join order_payment on order_payment.order_sn = oi.order_sn order by order_return.add_time DESC limit N,N Count: 1 Time=1.00s (1s) Lock=0.00s (0s) Rows=1.0 (1), root[root]@localhost select sleep(N) Died at /usr/local/mysql/bin/mysqldumpslow line 161, chunk 236.看到后面还是报错:Died at /usr/local/mysql/bin/mysqldumpslow line 161, chunk 236.
4,去看看/usr/local/mysql/bin/mysqldumpslow的第161行左右,到底是在操作什么脚本。
156 my @sorted = sort { $stmt{$b}->{$opt{s}} $stmt{$a}->{$opt{s}} } keys %stmt; 157 @sorted = @sorted[0 .. $opt{t}-1] if $opt{t}; 158 @sorted = reverse @sorted if $opt{r}; 159 160 foreach (@sorted) { 161 my $v = $stmt{$_} || die; 162 my ($c, $t,$at, $l,$al, $r,$ar) = @{ $v }{qw(c t at l al r ar)}; 163 my @users = keys %{$v->{users}}; 164 my $user = (@users==1) ? $users[0] : sprintf "%dusers",scalar @users; 165 my @hosts = keys %{$v->{hosts}}; 166 my $host = (@hosts==1) ? $hosts[0] : sprintf "%dhosts",scalar @hosts; 167 printf "Count: %d Time=%.2fs (%ds) Lock=%.2fs (%ds) Rows=%.1f (%d), $user\@$host\n%s\n\n", 168 $c, $at,$t, $al,$l, $ar,$r, $_; 169 } 170 171 sub usage { 172 my $str= shift;看到主要是foreach (@sorted)遍历函数,也就是遍历到chunk 236的时候就died结束了,没有办法往下继续foreach了。因为以前写过代码,知道报错所在的这一行
my $v = $stmt{$_} || die;是遍历第一句,那么肯定是赋值语句,报错Died,chunk 236肯定是已经遍历到末尾没有数据了,看这个函数没有判断传入的参数是否为null的逻辑,所以当文件数据已经遍历完,但是命令还没有结束,所以继续遍历,遍历null的时候报错,所以进程中止了,解决办法就是做个限制不要遍历超过原始数据的字符串长度。那么我们再来看执行的命令:
/usr/local/mysql/bin/mysqldumpslow -s at -t 15 /root/db01-102-slow.log 有 -t 15这一句,那么就是要显示出前15个记录,那么如果我的slow.log统计出来只有12个不到15个,而这里有继续遍历到15的话,那进程肯定会Died。
所以这里有2个解决方法:
1 修改/usr/local/mysql/bin/mysqldumpslow里面的源代码,加null判断。
这个过程有些复杂,暂时略过吧,期待后续空了再研究。
2 修改命令 /usr/local/mysql/bin/mysqldumpslow -s at -t 15 /root/db01-102-slow.log ,把-t 15修改成-t 10或者-t 5试试。
试了好几次,发现临界点在-t 7上面,如下:
[root@slave~]# /usr/local/mysql/bin/mysqldumpslow -s at -t 8 /root/db01-102-slow.log Reading mysql slow query log from /root/db01-102-slow.log Count: 22 Time=13.20s (290s) Lock=0.00s (0s) Rows=10.0 (220), [dubbo]@2hosts select coupon_id, coupon_lot.coupon_lot_id, coupon_lot.remark, coupon.code, coupon_lot.coupon_type, coupon.state, coupon_lot.ckey, coupon_lot.cvalue, coupon_lot.discount, coupon_lot.type, coupon_lot.channel, coupon_lot.is_reusable, coupon_lot.start_datetime, coupon_lot.end_datetime, coupon_lot.create_datetime, coupon.update_datetime ,coupon_lot.department, coupon_lot.state as couponLotState, coupon_lot.create_operator,coupon_lot.coupon_category, coupon_lot.pdt_code,brand.brand_name,product_category.category_name from coupon_lot left join coupon on coupon.coupon_lot_id = coupon_lot.coupon_lot_id LEFT JOIN brand ON brand.brand_id=coupon_lot.brand_id LEFT JOIN product_category on product_category.category_id=coupon_lot.category_id group by coupon_lot.coupon_lot_id order by coupon_lot.create_datetime DESC limit N,N Count: 22 Time=9.61s (211s) Lock=0.00s (0s) Rows=1.0 (22), [dubbo]@2hosts select count(*) from coupon_lot left join coupon on coupon.coupon_lot_id = coupon_lot.coupon_lot_id LEFT JOIN brand ON brand.brand_id=coupon_lot.brand_id LEFT JOIN product_category on product_category.category_id=coupon_lot.category_id Count: 5 Time=2.47s (12s) Lock=0.00s (0s) Rows=0.0 (0), [dubbo]@2hosts select user_id, usename, nickname, password, user_group_id, realname, gender, email, mobilephone, birthday, province_id, city_id, district_id, marry, income, remarks, create_datetime, active_state, verityEmail, verityPhone, credit, last_login, last_ip, is_locked, channel, tag, union_partner_uuid, union_user_safekey, is_black, qq, weibo_id, verity_email_key, verity_phone_key, verity_email_datetime, verity_phone_datetime, verity_question, verity_answer, cps_code, cps_time_from, cps_time_to, cps_cookie, first_channel from user_info where mobilephone = 'S' and (channel is null or trim(channel) ='S') Count: 177 Time=1.40s (247s) Lock=0.00s (0s) Rows=1.0 (177), [xx]@2hosts select count(*) from user_info LEFT JOIN system_region a ON province_id =a.region_id LEFT JOIN system_region b ON city_id = b.region_id LEFT JOIN system_region c ON district_id = c.region_id Count: 1 Time=1.13s (1s) Lock=0.00s (0s) Rows=10.0 (10), [xx]@[xxx] select return_sn, relating_order_sn, return_from, oi.order_out_sn , add_time , return_type, return_pay, ui.usename as userName, return_consignee, return_goods_count , return_total_fee, total_paid, return_desc, return_order_status, return_pay_status , return_shipping_status, order_return.lock_operator, order_return.return_invoice_no from order_return LEFT JOIN order_info oi on order_return.relating_order_sn = oi.order_sn left join user_info ui on oi.user_id = ui.user_id left join order_payment on order_payment.order_sn = oi.order_sn order by order_return.add_time DESC , oi.order_sn limit N,N Count: 8 Time=1.09s (8s) Lock=0.00s (0s) Rows=10.0 (80), [xx]@2hosts select return_sn, relating_order_sn, return_from, oi.order_out_sn , add_time , return_type, return_pay, ui.usename as userName, return_consignee, return_goods_count , return_total_fee, total_paid, return_desc, return_order_status, return_pay_status , return_shipping_status, order_return.lock_operator, order_return.return_invoice_no from order_return LEFT JOIN order_info oi on order_return.relating_order_sn = oi.order_sn left join user_info ui on oi.user_id = ui.user_id left join order_payment on order_payment.order_sn = oi.order_sn order by order_return.add_time DESC limit N,N Count: 1 Time=1.00s (1s) Lock=0.00s (0s) Rows=1.0 (1), root[root]@localhost select sleep(N) Died at /usr/local/mysql/bin/mysqldumpslow line 161, chunk 236. -- 临界点 -t 7 [root@db-master-2 ~]# /usr/local/mysql/bin/mysqldumpslow -s at -t 7 /root/db01-102-slow.log Reading mysql slow query log from /root/db01-102-slow.log Count: 22 Time=13.20s (290s) Lock=0.00s (0s) Rows=10.0 (220), [xx]@2hosts select coupon_id, coupon_lot.coupon_lot_id, coupon_lot.remark, coupon.code, coupon_lot.coupon_type, coupon.state, coupon_lot.ckey, coupon_lot.cvalue, coupon_lot.discount, coupon_lot.type, coupon_lot.channel, coupon_lot.is_reusable, coupon_lot.start_datetime, coupon_lot.end_datetime, coupon_lot.create_datetime, coupon.update_datetime ,coupon_lot.department, coupon_lot.state as couponLotState, coupon_lot.create_operator,coupon_lot.coupon_category, coupon_lot.pdt_code,brand.brand_name,product_category.category_name from coupon_lot left join coupon on coupon.coupon_lot_id = coupon_lot.coupon_lot_id LEFT JOIN brand ON brand.brand_id=coupon_lot.brand_id LEFT JOIN product_category on product_category.category_id=coupon_lot.category_id group by coupon_lot.coupon_lot_id order by coupon_lot.create_datetime DESC limit N,N Count: 22 Time=9.61s (211s) Lock=0.00s (0s) Rows=1.0 (22), [dubbo]@2hosts select count(*) from coupon_lot left join coupon on coupon.coupon_lot_id = coupon_lot.coupon_lot_id LEFT JOIN brand ON brand.brand_id=coupon_lot.brand_id LEFT JOIN product_category on product_category.category_id=coupon_lot.category_id Count: 5 Time=2.47s (12s) Lock=0.00s (0s) Rows=0.0 (0), [xx]@2hosts select user_id, usename, nickname, password, user_group_id, realname, gender, email, mobilephone, birthday, province_id, city_id, district_id, marry, income, remarks, create_datetime, active_state, verityEmail, verityPhone, credit, last_login, last_ip, is_locked, channel, tag, union_partner_uuid, union_user_safekey, is_black, qq, weibo_id, verity_email_key, verity_phone_key, verity_email_datetime, verity_phone_datetime, verity_question, verity_answer, cps_code, cps_time_from, cps_time_to, cps_cookie, first_channel from user_info where mobilephone = 'S' and (channel is null or trim(channel) ='S') Count: 177 Time=1.40s (247s) Lock=0.00s (0s) Rows=1.0 (177), [xx]@2hosts select count(*) from user_info LEFT JOIN system_region a ON province_id =a.region_id LEFT JOIN system_region b ON city_id = b.region_id LEFT JOIN system_region c ON district_id = c.region_id Count: 1 Time=1.13s (1s) Lock=0.00s (0s) Rows=10.0 (10), [dubbo]@[xxx] select return_sn, relating_order_sn, return_from, oi.order_out_sn , add_time , return_type, return_pay, ui.usename as userName, return_consignee, return_goods_count , return_total_fee, total_paid, return_desc, return_order_status, return_pay_status , return_shipping_status, order_return.lock_operator, order_return.return_invoice_no from order_return LEFT JOIN order_info oi on order_return.relating_order_sn = oi.order_sn left join user_info ui on oi.user_id = ui.user_id left join order_payment on order_payment.order_sn = oi.order_sn order by order_return.add_time DESC , oi.order_sn limit N,N Count: 8 Time=1.09s (8s) Lock=0.00s (0s) Rows=10.0 (80), [dubbo]@2hosts select return_sn, relating_order_sn, return_from, oi.order_out_sn , add_time , return_type, return_pay, ui.usename as userName, return_consignee, return_goods_count , return_total_fee, total_paid, return_desc, return_order_status, return_pay_status , return_shipping_status, order_return.lock_operator, order_return.return_invoice_no from order_return LEFT JOIN order_info oi on order_return.relating_order_sn = oi.order_sn left join user_info ui on oi.user_id = ui.user_id left join order_payment on order_payment.order_sn = oi.order_sn order by order_return.add_time DESC limit N,N Count: 1 Time=1.00s (1s) Lock=0.00s (0s) Rows=1.0 (1), root[root]@localhost select sleep(N) [root@db-master-2 ~]#
最终总结:
mysqldumpslow报错:Died at /usr/local/mysql/bin/mysqldumpslow line 161, chunk 236. 是因为top数目太多了,mysqldumpslow遍历不过来的缘故。

MySQL和SQLite的主要区别在于设计理念和使用场景:1.MySQL适用于大型应用和企业级解决方案,支持高性能和高并发;2.SQLite适合移动应用和桌面软件,轻量级且易于嵌入。

MySQL中的索引是数据库表中一列或多列的有序结构,用于加速数据检索。1)索引通过减少扫描数据量提升查询速度。2)B-Tree索引利用平衡树结构,适合范围查询和排序。3)创建索引使用CREATEINDEX语句,如CREATEINDEXidx_customer_idONorders(customer_id)。4)复合索引可优化多列查询,如CREATEINDEXidx_customer_orderONorders(customer_id,order_date)。5)使用EXPLAIN分析查询计划,避

在MySQL中使用事务可以确保数据一致性。1)通过STARTTRANSACTION开始事务,执行SQL操作后用COMMIT提交或ROLLBACK回滚。2)使用SAVEPOINT可以设置保存点,允许部分回滚。3)性能优化建议包括缩短事务时间、避免大规模查询和合理使用隔离级别。

选择PostgreSQL而非MySQL的场景包括:1)需要复杂查询和高级SQL功能,2)要求严格的数据完整性和ACID遵从性,3)需要高级空间功能,4)处理大数据集时需要高性能。PostgreSQL在这些方面表现出色,适合需要复杂数据处理和高数据完整性的项目。

MySQL数据库的安全可以通过以下措施实现:1.用户权限管理:通过CREATEUSER和GRANT命令严格控制访问权限。2.加密传输:配置SSL/TLS确保数据传输安全。3.数据库备份和恢复:使用mysqldump或mysqlpump定期备份数据。4.高级安全策略:使用防火墙限制访问,并启用审计日志记录操作。5.性能优化与最佳实践:通过索引和查询优化以及定期维护兼顾安全和性能。

如何有效监控MySQL性能?使用mysqladmin、SHOWGLOBALSTATUS、PerconaMonitoringandManagement(PMM)和MySQLEnterpriseMonitor等工具。1.使用mysqladmin查看连接数。2.用SHOWGLOBALSTATUS查看查询数。3.PMM提供详细性能数据和图形化界面。4.MySQLEnterpriseMonitor提供丰富的监控功能和报警机制。

MySQL和SQLServer的区别在于:1)MySQL是开源的,适用于Web和嵌入式系统,2)SQLServer是微软的商业产品,适用于企业级应用。两者在存储引擎、性能优化和应用场景上有显着差异,选择时需考虑项目规模和未来扩展性。

在需要高可用性、高级安全性和良好集成性的企业级应用场景下,应选择SQLServer而不是MySQL。1)SQLServer提供企业级功能,如高可用性和高级安全性。2)它与微软生态系统如VisualStudio和PowerBI紧密集成。3)SQLServer在性能优化方面表现出色,支持内存优化表和列存储索引。


热AI工具

Undresser.AI Undress
人工智能驱动的应用程序,用于创建逼真的裸体照片

AI Clothes Remover
用于从照片中去除衣服的在线人工智能工具。

Undress AI Tool
免费脱衣服图片

Clothoff.io
AI脱衣机

Video Face Swap
使用我们完全免费的人工智能换脸工具轻松在任何视频中换脸!

热门文章

热工具

VSCode Windows 64位 下载
微软推出的免费、功能强大的一款IDE编辑器

Atom编辑器mac版下载
最流行的的开源编辑器

EditPlus 中文破解版
体积小,语法高亮,不支持代码提示功能

Dreamweaver CS6
视觉化网页开发工具

SublimeText3 英文版
推荐:为Win版本,支持代码提示!