Interdev debugger would not attach to process 
Author Message
 Interdev debugger would not attach to process

I use Interdev 6, on NT server 4 sp5, with IExplorer 5.
I have installed the de{*filter*} and enabled all as the MSDN says.
When I start the de{*filter*} from Interdev, the de{*filter*} starts, but
breakpoints do not work, as well as Stop or de{*filter*} statements  (The
breakpoints are shown with question mark and a message that they will not
be hit).
This is true for server breakpoints as well as for browser breakpoints.
It seems that the problem is that the de{*filter*} would not attach
automatically to the relevant process. If I attach the de{*filter*} manually to
the IExplorer or to the inetinfo processes, Stop statements work and I can
use breakpoints.
How can I cause the de{*filter*} to attach automatically to the relevant
processes?


Sun, 08 Sep 2002 03:00:00 GMT  
 Interdev debugger would not attach to process
Q252895 - PRB: VBScript 'Stop' Statement Does Not Start Script De{*filter*}
http://www.*-*-*.com/

KB article reference to the wscript _/D_ switch should be _//D_.

--
Mark L. Ferguson  Please reply in newsgroup
marfers notes for OE5 >   http://www.*-*-*.com/

Quote:

> I use Interdev 6, on NT server 4 sp5, with IExplorer 5.
> I have installed the de{*filter*} and enabled all as the MSDN says.
> When I start the de{*filter*} from Interdev, the de{*filter*} starts, but
> breakpoints do not work, as well as Stop or de{*filter*} statements  (The
> breakpoints are shown with question mark and a message that they will not
> be hit).
> This is true for server breakpoints as well as for browser breakpoints.
> It seems that the problem is that the de{*filter*} would not attach
> automatically to the relevant process. If I attach the de{*filter*} manually to
> the IExplorer or to the inetinfo processes, Stop statements work and I can
> use breakpoints.
> How can I cause the de{*filter*} to attach automatically to the relevant
> processes?



Sun, 08 Sep 2002 03:00:00 GMT  
 Interdev debugger would not attach to process
I have tried it but id does not work. First, I did not find this key in the
registry. I have created it, but it did not change the problem.
If I enable Just In Time debugging, the Stop will work, but will start up
another de{*filter*} window, and still the breakpoints which I define in the
original Interdev Debug window will not work. Do you have another Idea?



Q252895 - PRB: VBScript 'Stop' Statement Does Not Start Script De{*filter*}
http://www.*-*-*.com/

KB article reference to the wscript _/D_ switch should be _//D_.

--
Mark L. Ferguson  Please reply in newsgroup
marfers notes for OE5 >
http://www.*-*-*.com/

Quote:
> I use Interdev 6, on NT server 4 sp5, with IExplorer 5.
> I have installed the de{*filter*} and enabled all as the MSDN says.
> When I start the de{*filter*} from Interdev, the de{*filter*} starts, but
> breakpoints do not work, as well as Stop or de{*filter*} statements  (The
> breakpoints are shown with question mark and a message that they will
not
> be hit).
> This is true for server breakpoints as well as for browser breakpoints.
> It seems that the problem is that the de{*filter*} would not attach
> automatically to the relevant process. If I attach the de{*filter*} manually
to
> the IExplorer or to the inetinfo processes, Stop statements work and I can
> use breakpoints.
> How can I cause the de{*filter*} to attach automatically to the relevant
> processes?



Mon, 09 Sep 2002 03:00:00 GMT  
 Interdev debugger would not attach to process
I found this excerpt of KBase Q143180

The parameter location is under the HKEY_LOCAL_MACHINE subtree under the
following subkeys:

   \System\CurrentControlSet\Services\InetInfo\Parameters

DebugFlags specifies the bit mask for selectively enabling different checks in a
debug binary of the server common dll (INFOCOMM.DLL). This bit mask applies to
the common dll only.

   #define DEBUG_ERROR                                     0x00000008L
   #define DEBUG_ODBC                                      0x00000010L
   #define DEBUG_DLL_RPC                                   0x00000020L
   #define DEBUG_GATEWAY                                   0x00010000L
   #define DEBUG_INETLOG                                   0x00020000L
   #define DEBUG_ATQ                                       0x00040000L
   #define DEBUG_DLL_EVENT_LOG                             0x00100000L
   #define DEBUG_DLL_SERVICE_INFO                          0x00200000L
   #define DEBUG_DLL_SECURITY                              0x00400000L
   #define DEBUG_DLL_CONNECTION                            0x00800000L
   #define DEBUG_DLL_SOCKETS                               0x01000000L
   #define DEBUG_HEAP_FILL                                 0x02000000L
   #define DEBUG_HEAP_MSG                                  0x04000000L
   #define DEBUG_HEAP_CHECK                                0x08000000L
   #define DEBUG_MIME_MAP                                  0x10000000L
   #define DEBUG_DLL_VIRTUAL_ROOTS                         0x20000000L

--
Mark L. Ferguson  Please reply in newsgroup
marfers notes for OE5 >   http://www.*-*-*.com/

Quote:

> I have tried it but id does not work. First, I did not find this key in the
> registry. I have created it, but it did not change the problem.
> If I enable Just In Time debugging, the Stop will work, but will start up
> another de{*filter*} window, and still the breakpoints which I define in the
> original Interdev Debug window will not work. Do you have another Idea?



> Q252895 - PRB: VBScript 'Stop' Statement Does Not Start Script De{*filter*}
> http://www.*-*-*.com/

> KB article reference to the wscript _/D_ switch should be _//D_.

> --
> Mark L. Ferguson  Please reply in newsgroup
> marfers notes for OE5 >
> http://www.*-*-*.com/


> > I use Interdev 6, on NT server 4 sp5, with IExplorer 5.
> > I have installed the de{*filter*} and enabled all as the MSDN says.
> > When I start the de{*filter*} from Interdev, the de{*filter*} starts, but
> > breakpoints do not work, as well as Stop or de{*filter*} statements  (The
> > breakpoints are shown with question mark and a message that they will
> not
> > be hit).
> > This is true for server breakpoints as well as for browser breakpoints.
> > It seems that the problem is that the de{*filter*} would not attach
> > automatically to the relevant process. If I attach the de{*filter*} manually
> to
> > the IExplorer or to the inetinfo processes, Stop statements work and I can
> > use breakpoints.
> > How can I cause the de{*filter*} to attach automatically to the relevant
> > processes?



Mon, 09 Sep 2002 03:00:00 GMT  
 Interdev debugger would not attach to process
Thank you Mark!
The last advice helped a little, but the problem was not solved completely.
I have created the "DebugFlags" value in the appropriate place, and gave it
the value 0xffffffff.
Now, when I start the de{*filter*}, I see that the application is run in a
separate process (I see it in the MMS: The "Run in separate memory space" is
checked), an two processes are attached to the de{*filter*}: iexplorer and
inetinfo.
But, when a Stop statement is hit, the Explorer ask me if I want to debug
the application, and if I say yes, it opens another de{*filter*}.
When the stop is hit, I see another process which is not attached to the
de{*filter*}: mfx. If I attach this process manually to the de{*filter*}, I am not
asked if I want to debug the application, but the original de{*filter*} is
stopped automatically on the Stop statement.
Nevertheless, breakpoints still do not work: when the Stop statement is hit,
I find myself in a window headed "(VBScript - script block)", and this
window I can define new breakpoints ant they work. But the original
breakpoints does not work, and when the script is done, the script window is
closed, the new breakpoints disappear (they do not wxist any more even if
the script window is opened again). Of course, I have checked the option:
"Insert breakpoints in Active Server Pages for breakpoints in client
script" - but this seems irrelevant, since the Stop statement was in server
script.
Breakpoints in client script did not work too, but "de{*filter*}" statement
worked.
How can I cause the de{*filter*} to attach automatically to all the relevant
processes, and how can I cause breakpoints to work?



I found this excerpt of KBase Q143180

The parameter location is under the HKEY_LOCAL_MACHINE subtree under the
following subkeys:

   \System\CurrentControlSet\Services\InetInfo\Parameters

DebugFlags specifies the bit mask for selectively enabling different checks
in a
debug binary of the server common dll (INFOCOMM.DLL). This bit mask applies
to
the common dll only.

   #define DEBUG_ERROR                                     0x00000008L
   #define DEBUG_ODBC                                      0x00000010L
   #define DEBUG_DLL_RPC                                   0x00000020L
   #define DEBUG_GATEWAY                                   0x00010000L
   #define DEBUG_INETLOG                                   0x00020000L
   #define DEBUG_ATQ                                       0x00040000L
   #define DEBUG_DLL_EVENT_LOG                             0x00100000L
   #define DEBUG_DLL_SERVICE_INFO                          0x00200000L
   #define DEBUG_DLL_SECURITY                              0x00400000L
   #define DEBUG_DLL_CONNECTION                            0x00800000L
   #define DEBUG_DLL_SOCKETS                               0x01000000L
   #define DEBUG_HEAP_FILL                                 0x02000000L
   #define DEBUG_HEAP_MSG                                  0x04000000L
   #define DEBUG_HEAP_CHECK                                0x08000000L
   #define DEBUG_MIME_MAP                                  0x10000000L
   #define DEBUG_DLL_VIRTUAL_ROOTS                         0x20000000L

--
Mark L. Ferguson  Please reply in newsgroup
marfers notes for OE5 >
http://www.*-*-*.com/

Quote:
> I have tried it but id does not work. First, I did not find this key in
the
> registry. I have created it, but it did not change the problem.
> If I enable Just In Time debugging, the Stop will work, but will start up
> another de{*filter*} window, and still the breakpoints which I define in the
> original Interdev Debug window will not work. Do you have another Idea?



> Q252895 - PRB: VBScript 'Stop' Statement Does Not Start Script De{*filter*}
> http://www.*-*-*.com/

> KB article reference to the wscript _/D_ switch should be _//D_.

> --
> Mark L. Ferguson  Please reply in newsgroup
> marfers notes for OE5 >
> http://www.*-*-*.com/


> > I use Interdev 6, on NT server 4 sp5, with IExplorer 5.
> > I have installed the de{*filter*} and enabled all as the MSDN says.
> > When I start the de{*filter*} from Interdev, the de{*filter*} starts, but
> > breakpoints do not work, as well as Stop or de{*filter*} statements
(The
> > breakpoints are shown with question mark and a message that they will
> not
> > be hit).
> > This is true for server breakpoints as well as for browser breakpoints.
> > It seems that the problem is that the de{*filter*} would not attach
> > automatically to the relevant process. If I attach the de{*filter*} manually
> to
> > the IExplorer or to the inetinfo processes, Stop statements work and I
can
> > use breakpoints.
> > How can I cause the de{*filter*} to attach automatically to the relevant
> > processes?



Mon, 09 Sep 2002 03:00:00 GMT  
 Interdev debugger would not attach to process
I don't know what conflict exists in your settings. You should be able to do all that without trouble.

--
Mark L. Ferguson  Please reply in newsgroup
marfers notes for OE5 >   http://www.*-*-*.com/

Quote:

> Thank you Mark!
> The last advice helped a little, but the problem was not solved completely.
> I have created the "DebugFlags" value in the appropriate place, and gave it
> the value 0xffffffff.
> Now, when I start the de{*filter*}, I see that the application is run in a
> separate process (I see it in the MMS: The "Run in separate memory space" is
> checked), an two processes are attached to the de{*filter*}: iexplorer and
> inetinfo.
> But, when a Stop statement is hit, the Explorer ask me if I want to debug
> the application, and if I say yes, it opens another de{*filter*}.
> When the stop is hit, I see another process which is not attached to the
> de{*filter*}: mfx. If I attach this process manually to the de{*filter*}, I am not
> asked if I want to debug the application, but the original de{*filter*} is
> stopped automatically on the Stop statement.
> Nevertheless, breakpoints still do not work: when the Stop statement is hit,
> I find myself in a window headed "(VBScript - script block)", and this
> window I can define new breakpoints ant they work. But the original
> breakpoints does not work, and when the script is done, the script window is
> closed, the new breakpoints disappear (they do not wxist any more even if
> the script window is opened again). Of course, I have checked the option:
> "Insert breakpoints in Active Server Pages for breakpoints in client
> script" - but this seems irrelevant, since the Stop statement was in server
> script.
> Breakpoints in client script did not work too, but "de{*filter*}" statement
> worked.
> How can I cause the de{*filter*} to attach automatically to all the relevant
> processes, and how can I cause breakpoints to work?



> I found this excerpt of KBase Q143180

> The parameter location is under the HKEY_LOCAL_MACHINE subtree under the
> following subkeys:

>    \System\CurrentControlSet\Services\InetInfo\Parameters

> DebugFlags specifies the bit mask for selectively enabling different checks
> in a
> debug binary of the server common dll (INFOCOMM.DLL). This bit mask applies
> to
> the common dll only.

>    #define DEBUG_ERROR                                     0x00000008L
>    #define DEBUG_ODBC                                      0x00000010L
>    #define DEBUG_DLL_RPC                                   0x00000020L
>    #define DEBUG_GATEWAY                                   0x00010000L
>    #define DEBUG_INETLOG                                   0x00020000L
>    #define DEBUG_ATQ                                       0x00040000L
>    #define DEBUG_DLL_EVENT_LOG                             0x00100000L
>    #define DEBUG_DLL_SERVICE_INFO                          0x00200000L
>    #define DEBUG_DLL_SECURITY                              0x00400000L
>    #define DEBUG_DLL_CONNECTION                            0x00800000L
>    #define DEBUG_DLL_SOCKETS                               0x01000000L
>    #define DEBUG_HEAP_FILL                                 0x02000000L
>    #define DEBUG_HEAP_MSG                                  0x04000000L
>    #define DEBUG_HEAP_CHECK                                0x08000000L
>    #define DEBUG_MIME_MAP                                  0x10000000L
>    #define DEBUG_DLL_VIRTUAL_ROOTS                         0x20000000L

> --
> Mark L. Ferguson  Please reply in newsgroup
> marfers notes for OE5 >
> http://www.*-*-*.com/


> > I have tried it but id does not work. First, I did not find this key in
> the
> > registry. I have created it, but it did not change the problem.
> > If I enable Just In Time debugging, the Stop will work, but will start up
> > another de{*filter*} window, and still the breakpoints which I define in the
> > original Interdev Debug window will not work. Do you have another Idea?



> > Q252895 - PRB: VBScript 'Stop' Statement Does Not Start Script De{*filter*}
> > http://www.*-*-*.com/

> > KB article reference to the wscript _/D_ switch should be _//D_.

> > --
> > Mark L. Ferguson  Please reply in newsgroup
> > marfers notes for OE5 >
> > http://www.*-*-*.com/


> > > I use Interdev 6, on NT server 4 sp5, with IExplorer 5.
> > > I have installed the de{*filter*} and enabled all as the MSDN says.
> > > When I start the de{*filter*} from Interdev, the de{*filter*} starts, but
> > > breakpoints do not work, as well as Stop or de{*filter*} statements
> (The
> > > breakpoints are shown with question mark and a message that they will
> > not
> > > be hit).
> > > This is true for server breakpoints as well as for browser breakpoints.
> > > It seems that the problem is that the de{*filter*} would not attach
> > > automatically to the relevant process. If I attach the de{*filter*} manually
> > to
> > > the IExplorer or to the inetinfo processes, Stop statements work and I
> can
> > > use breakpoints.
> > > How can I cause the de{*filter*} to attach automatically to the relevant
> > > processes?



Mon, 09 Sep 2002 03:00:00 GMT  
 Interdev debugger would not attach to process
Microsoft has confirmed this to be a bug, when using IExplorer 5, in the
MSDN knowledge base: "BUG: Client-Side Breakpoints in Active Server Pages
Not Hit with Internet Explorer 5 Installed" (ID: Q233035)
I suspect that there are more bugs concerning breakpoints in ASP server
code.
The solution is to attach the de{*filter*} manualy.



I don't know what conflict exists in your settings. You should be able to do
all that without trouble.

--
Mark L. Ferguson  Please reply in newsgroup
marfers notes for OE5 >
http://www.*-*-*.com/

Quote:
> Thank you Mark!
> The last advice helped a little, but the problem was not solved
completely.
> I have created the "DebugFlags" value in the appropriate place, and gave
it
> the value 0xffffffff.
> Now, when I start the de{*filter*}, I see that the application is run in a
> separate process (I see it in the MMS: The "Run in separate memory space"
is
> checked), an two processes are attached to the de{*filter*}: iexplorer and
> inetinfo.
> But, when a Stop statement is hit, the Explorer ask me if I want to debug
> the application, and if I say yes, it opens another de{*filter*}.
> When the stop is hit, I see another process which is not attached to the
> de{*filter*}: mfx. If I attach this process manually to the de{*filter*}, I am not
> asked if I want to debug the application, but the original de{*filter*} is
> stopped automatically on the Stop statement.
> Nevertheless, breakpoints still do not work: when the Stop statement is
hit,
> I find myself in a window headed "(VBScript - script block)", and this
> window I can define new breakpoints ant they work. But the original
> breakpoints does not work, and when the script is done, the script window
is
> closed, the new breakpoints disappear (they do not wxist any more even if
> the script window is opened again). Of course, I have checked the option:
> "Insert breakpoints in Active Server Pages for breakpoints in client
> script" - but this seems irrelevant, since the Stop statement was in
server
> script.
> Breakpoints in client script did not work too, but "de{*filter*}" statement
> worked.
> How can I cause the de{*filter*} to attach automatically to all the relevant
> processes, and how can I cause breakpoints to work?



> I found this excerpt of KBase Q143180

> The parameter location is under the HKEY_LOCAL_MACHINE subtree under the
> following subkeys:

>    \System\CurrentControlSet\Services\InetInfo\Parameters

> DebugFlags specifies the bit mask for selectively enabling different
checks
> in a
> debug binary of the server common dll (INFOCOMM.DLL). This bit mask
applies
> to
> the common dll only.

>    #define DEBUG_ERROR                                     0x00000008L
>    #define DEBUG_ODBC                                      0x00000010L
>    #define DEBUG_DLL_RPC                                   0x00000020L
>    #define DEBUG_GATEWAY                                   0x00010000L
>    #define DEBUG_INETLOG                                   0x00020000L
>    #define DEBUG_ATQ                                       0x00040000L
>    #define DEBUG_DLL_EVENT_LOG                             0x00100000L
>    #define DEBUG_DLL_SERVICE_INFO                          0x00200000L
>    #define DEBUG_DLL_SECURITY                              0x00400000L
>    #define DEBUG_DLL_CONNECTION                            0x00800000L
>    #define DEBUG_DLL_SOCKETS                               0x01000000L
>    #define DEBUG_HEAP_FILL                                 0x02000000L
>    #define DEBUG_HEAP_MSG                                  0x04000000L
>    #define DEBUG_HEAP_CHECK                                0x08000000L
>    #define DEBUG_MIME_MAP                                  0x10000000L
>    #define DEBUG_DLL_VIRTUAL_ROOTS                         0x20000000L

> --
> Mark L. Ferguson  Please reply in newsgroup
> marfers notes for OE5 >
> http://www.*-*-*.com/


> > I have tried it but id does not work. First, I did not find this key in
> the
> > registry. I have created it, but it did not change the problem.
> > If I enable Just In Time debugging, the Stop will work, but will start
up
> > another de{*filter*} window, and still the breakpoints which I define in the
> > original Interdev Debug window will not work. Do you have another Idea?



> > Q252895 - PRB: VBScript 'Stop' Statement Does Not Start Script De{*filter*}
> > http://www.*-*-*.com/

> > KB article reference to the wscript _/D_ switch should be _//D_.

> > --
> > Mark L. Ferguson  Please reply in newsgroup
> > marfers notes for OE5 >
> > http://www.*-*-*.com/


> > > I use Interdev 6, on NT server 4 sp5, with IExplorer 5.
> > > I have installed the de{*filter*} and enabled all as the MSDN says.
> > > When I start the de{*filter*} from Interdev, the de{*filter*} starts, but
> > > breakpoints do not work, as well as Stop or de{*filter*} statements
> (The
> > > breakpoints are shown with question mark and a message that they
will
> > not
> > > be hit).
> > > This is true for server breakpoints as well as for browser
breakpoints.
> > > It seems that the problem is that the de{*filter*} would not attach
> > > automatically to the relevant process. If I attach the de{*filter*}
manually
> > to
> > > the IExplorer or to the inetinfo processes, Stop statements work and I
> can
> > > use breakpoints.
> > > How can I cause the de{*filter*} to attach automatically to the relevant
> > > processes?



Sun, 15 Sep 2002 03:00:00 GMT  
 
 [ 7 post ] 

 Relevant Pages 

1. Interdev debugger would not attach to process

2. Interdev debugger would not attach to process

3. Using Interdev as Debugger

4. Debugger attach causing precision difference?

5. Attached table and not attached table

6. Attach to a running process? (Using code)

7. Attaching to a running VB process

8. SQL Debugger: SFI Announces New Debugger Capability To be Included in SQL-Programmer 2.5 This Summer

9. Design Controls in Interdev do not work...

10. Help - Interdev not finding Server!

11. Changing MS Visual InterDev IE4.0 debugger to IE5.0 debugger ?

12. Changing MS Visual InterDev IE4.0 debugger to IE5.0 debugger ?

 

 
Powered by phpBB® Forum Software