Windebug debugging-breakpoint 4's offset expression evaluation failed.

This problem occurs in recent debugging. I always blame the PDB file problem and re-compiled it n times.

At first, I ignored this error, so I had to re-compile the PDB.

The first error code found today is really very important.

Then I started to ask du Niang for help. Soon I solved the problem because of incorrect breakpoint settings.

//////////////////////////////////////// /////////////

From: http://blog.csdn.net/lijiawlm/article/details/4412289

// Repost the article

Basic knowledge

 

Lower breakpoint during BP program running

Breakpoint before Bu program is loaded

BL list all breakpoints

BC clear breakpoint

 

When debugging the driver today, I found that debugging fails after the breakpoint is fixed.

Windbg display

 

Kd> G
Breakpoint 11's offset expression evaluation failed.
Check for invalid symbols or bad syntax.
Waitforevent failed
NT! Debugservice2 + 0x11:

 

Literally, it means there is a problem with the 11th breakpoint.

So the operation instructions for searching windbg online

One thing I found is the basic knowledge above.

The following describes the solution process.

First

Kd> BL
0 EU 0001 (0001) (@ MASM ('helloddk! Driver. cpp: 35 + '))
1 EU 0001 (0001) (helloddk! DriverEntry)
2 EU 0001 (0001) (helloddk! DriverEntry)
3 EU 0001 (0001) (helloddk! DriverEntry)
4 E f9ed4890 0001 (0001) myddk! DriverEntry
5 EU 0001 (0001) (helloddk! DriverEntry)
6 E f9ed49000001 (0001) myddk! Createdevice
7 EU 0001 (0001) (test! DriverEntry)
8 EU 0001 (0001) (driver! DriverEntry)
9 EU 0001 (0001) (@ MASM ('driver. cpp: 18 + '))
10 E f9ed4890 0001 (0001) myddk! DriverEntry
11 EU 0001 (0001) (myddk! Lcreatefile)
12 E f9ed4890 0001 (0001) myddk! DriverEntry
13 E f9ed4890 0001 (0001) myddk! DriverEntry
14 E f9ed4890 0001 (0001) myddk! DriverEntry
15 E f9ed48ad 0001 (0001) myddk! DriverEntry + 0x1d

 

It is found that there are many places where there is no address. It should be because the breakpoint in these areas is deleted due to a problem.

Kd> BC 0 1 2 3 5 7 8 9
Kd> BL
4 E f9ed4890 0001 (0001) myddk! DriverEntry
6 E f9ed49000001 (0001) myddk! Createdevice
10 E f9ed4890 0001 (0001) myddk! DriverEntry
12 E f9ed4890 0001 (0001) myddk! DriverEntry
13 E f9ed4890 0001 (0001) myddk! DriverEntry
14 E f9ed4890 0001 (0001) myddk! DriverEntry
15 E f9ed48ad 0001 (0001) myddk! DriverEntry + 0x1d

 

Continue

Kd> G
Can run