We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Before building make sure you set environment variable NODE_PTY_DEBUG to 1 to trigger a debug build.
NODE_PTY_DEBUG
Download WinDbg: https://www.microsoft.com/en-us/p/windbg-preview/9pgjgd53tn86?rtc=1&activetab=pivot%3Aoverviewtab
Build and run WinDbgX.exe node .\examples\fork\index.js
WinDbgX.exe node .\examples\fork\index.js
One time setup to set paths:
Open File > Settings, go to Debugging settings and set:
File > Settings
Debugging settings
Break when pty.node is loaded:
sxe ld pty
Go (and break at pty.node):
g
List modules (verify pty.node is loaded):
lm
Reload symbols:
.reload /f
Examine a function:
x pty!PtyStartProcess
You can then open the file by clicking pty!PtyStartProcess and ...\src\win\pty.cc links. Set a breakpoint by left clicking the gutter.
pty!PtyStartProcess
...\src\win\pty.cc
Go:
On Windows, you can show the winpty agent console window by adding the environment variable WINPTY_SHOW_CONSOLE=1 to the pty's environment. See https://github.com/rprichard/winpty#debugging-winpty for more information.
WINPTY_SHOW_CONSOLE=1