Attaching Microsoft Script Debugger to a Running Process
OK, I’ve just learnt how to do something that I’m going to find very useful in the future! I’ve wanted to do this for a while and didn’t know, but necessity is the mother of invention (or investigation in this case.)
Here’s the scenario. I have a running Internet Explorer session connected to a Live environment. I cannot change the Live code to add in a “Stop” statement. That Internet Explorer session is actually a hosted version of the IE ActiveX control inside of a custom executable. I have a VBScript bug and I need to see what’s happening.
So, what I need to do is to attached Microsoft Script Debugger (MSD) to the running IE session, and force a breakpoint in the code. Here’s how….
- Start MSD.
- Go to “Debug” -> “Processes”.
- Find the appropriate process, use the “Title” column to help.
- Click “Attach”.
- When the “Attach to Process” screen is displayed, click “OK”.
- Click “Close”
That will now attach you to the correct process. All you need to do now is to add a break point.
- Go to “Debug” -> “New Breakpoint”
- Type in the name of a function, sub-routine or event that you want to trap.
- Perform the actions in IE that would cause the function where you inserted the breakpoint to fire.
- You should then be directed to MSD with the source code of the lines where you inserted the break point.
- Step-Over, Out-of or Into as much as you’d like!
Simple really – just needed five minutes of Googling and playing around in MSD!


