How to turn off the debug message of the MTD driver

Is it a driver? After the installation of the graphics card, you can use the graphics card test software to test the sound card can have sound without noise, and the network card can access the Internet normally, and you can generally have a corresponding test.

Please explain the problem clearly, the driver cannot be debugged. Not sure what you're asking.

What you said upstairs is too troublesome.

It's no wonder that ordinary people can understand it.

Just ask how to use debug.

In fact, if you want to see some operations before the system is shut down, you can use the event viewer ah computer management, which has the event viewer option.

Enter event 6006 in the system to check the shutdown time.

When configuring a WebLogic domain, do not select the product mode, select the development mode, and then start it with debug, instead of starting directly

1.Compile your driver, let's say it's named, and send the driver symbol file to the mysyssymbols folder (your own debug symbol folder you set earlier).

2.Start the virtual machine and select the debugging mode to enter the system.

3.In WindBG, press Ctrl+Break and type bu showssdt!DriverEntry: Enter to confirm, and then enter the G command to continue.

4.Drag and drop the driver into the virtual machine (you can also copy the driver file through the network neighbor, start instdrv in the virtual machine system, and load the driver (you can also install the driver as a service to the system and then use the net start driver name or net stop driver name).

5.Go back to the windbg window, and if everything is fine, you'll see that you've broken off at the entrance.

Next, it's up to you whether you want to take a single step, break a point, continue to execute, or whatever

f9 sets the breakpoint, and if you press it once, the breakpoint will be canceled.

F10 steps forward, that is, single-step, encounters a function (call instruction), does not enter the function inside, but continues to work after the function returns.

f11 enters the function in a single step, that is, it is executed in a single step, and when it encounters a function (call instruction), it enters the function and continues to step forward.

debug->break debugging (breakpoint can only be set in case of break).

This is a common error, and the Windows prompt is not an internal or external command, nor is it a runnable program or batch file. This means that the command you entered does not point to a file or is not an internal command.

Here is an explanation of what internal commands are, as early as the DOS era, in order to facilitate the operation of users, Microsoft has integrated some commonly used commands, such as dir, cd and other commands into the system. This is a big plus for DOS. The file that stores these internal commands is "probably a file name like this, which I can't remember because it's been too long to remember."

Together with , it became one of the three important documents of the DOS system. When you enter any command in the DOS system, the system will first look for the command from the file, and then turn to the external command, and after the XP era, the internal command file is integrated into the system.

External commands are actually executable files (.).exe file), program file (..)com file), and batch files (.).bat）

When you type a debug command, the system will look for it in the internal commands first, and if you don't find the command you entered in the internal commands, then the system will move to the external command. That is, the system will look for these external commands in the directory to which the "path" environment variable points to. If it is not found, it says "Not an internal or external command, nor a runnable program or batch file".

Understanding the principle, the solution is very simple, and there are generally two reasons:

First: There is a missing file in your system directory.

Second: If a file exists, but the path environment variable does not point to the directory of the file.

So the landlord is sure to check whether there are any files in your system directory (the owner of the system directory should know, C: Windows). If you don't have one, copy it from another computer to your computer and put it in the same directory location.

If there is, look at the path environment variable again, and put %systemroot% system32; %systemroot%;% is added to it, and if there is such content, there is no need to add it.

In short, make sure that there is a file, and make sure that the path environment variable points to the directory of the file.

Once you get it done, the debug command will definitely be executed successfully.

The system does not support that command. The system does not have that command by default.

1. Take advantage of printk 2, view OOP messages 3, use strace 4, take advantage of the kernel's built-in hacking options 5, use IOCTL methods 6, and use the proc file system.

Want to switch to windbg, but don't know how difficult it is? I don't know if there are any good tutorials to introduce them.