Inside Windows Debugging 001Tweet
Recently I’ve started reading “Inside Windows Debugging” to enhance my debugging skills. I had some trouble in
PART 2 Debugging for Fun and Profit – Listing Parameters and Locals for Your Own Code
so I’m going to leave a note how I got through it.
The problem occurred when I tried to set a breakpoint on the “kernel32!CreateProcessW”. (below is the command)
But all I got was a messages indicating some kind of error.
0:000> bp kernel32!createprocessw
Couldn’t resolve error at ‘kernel32!createprocessw’
As expected, after I continued with the “g” command, the breakpoint didn’t seem to work.
Little knowledge did I have but I started by finding the kernel32!CreateProcess functions with the “x” command.
0:000> x kernel32!CreateProcess*
76b90cb9 KERNEL32!CreateProcessWithTokenW (void)
76b90d84 KERNEL32!CreateProcessAsUserW (void)
76b90d84 KERNEL32!CreateProcessWithLogonW (void)
76b4e225 KERNEL32!CreateProcessWStub =
76b72e04 KERNEL32!CreateProcessInternalAStub = 76b72e15 KERNEL32!CreateProcessInternalWStub = 76b72de2 KERNEL32!CreateProcessAStub = 76b72df3 KERNEL32!CreateProcessAsUserWStub =
There was no “kernel32!CreateProcessW” in the functions list so this was probably the cause of the error above. Well, I had no clue which function inside of these was the right one to call but luckily I chose “kernel32!CreateProcessWStub”.
0:000> bp kernel32!createprocesswstub
ModLoad: 76ee0000 76f05000 C:\WINDOWS\SysWOW64\IMM32.DLL
ModLoad: 74ca0000 74d97000 C:\WINDOWS\SysWOW64\MSCTF.dll
Breakpoint 0 hit
eax=001bfcec ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 edi=001bfd40
eip=76b4e225 esp=001bfcb8 ebp=001bfd40 iopl=0 nv up ei pl nz ac pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000216
76b4e225 8bff mov edi,edi
001bfcb4 002a1732 KERNEL32!CreateProcessWStub
wchar_t * pwszCommandLine = 0x003571c0 “notepad.exe”,
unsigned long dwCreationFlags = 0,
void ** phProcess = 0x001bfde0,
void ** phPrimaryThread = 0x001bfdd8)+0x47 [c:\book\code\chapter_01\workerprocess\main.cpp @ 94]
The breakpoint worked as expected and you could see that the “notepad” process was created using the “kernel32!CreateProcessWStub”. Maybe kernel32!CreateProcessW got deprecated in Windows 8.1??? No clue for this moment.