A few days before the holiday, it took about two days to locate the bug, and it took 20 minutes to modify the bug. After the holiday, I finally decided to carefully learn the debug technology. The following are some useful materials:
<Advanced Windows debugging>
<Inside Windows debugging: A Practical Guide to debugging and tracing strategies in Windows>
Amazon has a high rating on both books, both written by debugging experts in MS, but it is a pity that the first book has been published earlier. Some tools are now greatly changed. If time is limited, we recommend that you read the second one first. Both of these books involve a lot of technical details, such as Windows principles and compilations. You have to wait and take a look at them. The old man started with a few chapters and won't be able to understand them later -. -
In addition, from last year to now, Channel 9 has a program called defrag tool which is quite good. It has introduced almost all the tools used to solve Windows PC problems, which are collected every Monday and are now in 30 phases. The content ranges from basic process monitor to dump files, application Verifier tool, windbg, and so on. If you are good at English, it is strongly recommended!
PS: the third part of divinity2 rendering process analysis was accidentally deleted after I wrote it. Wait a few days -. -