Initial breakpoint of JIT

The Internet is good, and suddenly ie crash, windbg is automatically started as JIT, and subconscious input! Runaway ,~ * View the kV and find that all threads are in Ntdll! Kifastsystemcallret, that is, in the kernel, the time is very strange. How does ie crash? With this problem, lunch is not good.

 

After a long time, I suddenly realized it. At that time, the breakpoint should be the initial breakpoint, that is, NTDLL! Dbguiremotebreakin, and the real culprit should need to G again to skip this meaningless initial breakpoint. Although ie was gone at that time, fortunately dump was left and windbg was used to open it ~ * After all, there are 37 threads.

Although the crash command cannot be found in the analysis of dump, there is always something to look. History can be traced from the stack. Locate a line,

 

0aed50f4 76ee5e4c 750c6872 00000002 0aed5148 NTDLL! Kifastsystemcallret (FPO: [0, 0])
0aed50f8 750c6872 00000002 0aed5148 00000001 NTDLL! Ntwaitformultipleobjects + 0xc (FPO: [5, 0])
...

 

Full text see http://user.qzone.qq.com/31731705/blog/1297325245