When trying to debug the Windows 7 kernel using livekd, the following message is always displayed:
Cocould not resolve symbol file for ntoskrnl.exe: matrix Database
In this way, there is no ntoskrnl in the symbol file directory. the Directory of the pdb, so a lot of Windows Internals experiments have not been done. Today, I searched for a solution on the Internet and found a foreigner using Windbg to debug other problems of livekd...
To be honest, I felt quite ashamed to say that... having encountered a problem for more than half a month, I have never thought about using a debugger to keep up... I am always complacent when comparing with my classmates and some teachers who are crazy about playing Oolong in class. In fact, I know the level of my classmates, on average, there are also a number of students in Chinese universities. As a result, even the basic solutions are missing when a problem occurs, and there is no room for shame -_-
So we also take Windbg out and follow it, even if we don't get familiar with it slowly... however, when Windbg is used to start livekd, it even began to download the new symbol file for a long time. After the download, I still don't forget to start the kd...
What's more strange is that livekd has downloaded the ntkrpamp symbol file-_-which will not be the Union of ntosknl, ntkrnlpa, ntkrpamp, and ntkrnlmp? Or simply inherit the XP Name ...?
Source: http://www.cnblogs.com/snakewind/