1 Solution
Thank you for providing more information.
There can be lots of other reasons for the long delay. I'd like to narrow it down with you by trying the following steps:
i) Please create a simple C/C++ "hello world" project (using VS compiler). Set a BP @ main and start the debugger. If there's the same latency the root cause is related to global configuration/environment.
ii) If not, try a simple Fortran "hello world" project (using IFORT) instead. Again, start the debugger. In case latency is experienced now, it's related to Fortran extensions, high likely because of the plug-ins.
iii) And last, if the steps above did not reproduce the problem, it must be related to your project.
Solutions:
If there's latency for case i), please check VS configuration. Maybe external symbols files are retrieved, e.g. via HTTP or network share.
(You'll find this configuration via "Tools->Options...;Debugging/Symbols")
Deactivate it or use caching instead.
In case there's latency for ii), you can temporarily deactivate our Fortran expression evaluation (FEE) plug-in by renaming ForDbgSW.dll (\Common7\Packages\Debugger\ForDbgSW.dll) to DONTUSE_ForDbgSW.dll. Please do that only with VS closed. Afterwards, start VS again and try to debug. I'd assume the latency is gone for this case now. Close VS again and rename the DLL back.
FEE is used for evaluations/watches/autos/... for all Fortran applications. Maybe there are windows open that make use of it (Autos, Locals, Watches, BPs, ...). Let me know if the problem still exists with just the source window open when starting & running the debugger.
If latency exists only for case iii):
Are there any dependencies on network shares? VS does not work well if projects or other components are stored non-local.
Please let me know about the result.
Best regards,
Georg Zitzlsberger
There can be lots of other reasons for the long delay. I'd like to narrow it down with you by trying the following steps:
i) Please create a simple C/C++ "hello world" project (using VS compiler). Set a BP @ main and start the debugger. If there's the same latency the root cause is related to global configuration/environment.
ii) If not, try a simple Fortran "hello world" project (using IFORT) instead. Again, start the debugger. In case latency is experienced now, it's related to Fortran extensions, high likely because of the plug-ins.
iii) And last, if the steps above did not reproduce the problem, it must be related to your project.
Solutions:
If there's latency for case i), please check VS configuration. Maybe external symbols files are retrieved, e.g. via HTTP or network share.
(You'll find this configuration via "Tools->Options...;Debugging/Symbols")
Deactivate it or use caching instead.
In case there's latency for ii), you can temporarily deactivate our Fortran expression evaluation (FEE) plug-in by renaming ForDbgSW.dll (
FEE is used for evaluations/watches/autos/... for all Fortran applications. Maybe there are windows open that make use of it (Autos, Locals, Watches, BPs, ...). Let me know if the problem still exists with just the source window open when starting & running the debugger.
If latency exists only for case iii):
Are there any dependencies on network shares? VS does not work well if projects or other components are stored non-local.
Please let me know about the result.
Best regards,
Georg Zitzlsberger
Link Copied
Hello,
there can be various reasons why it (suddenly?) takes longer to start a debugging session. Let's start with something I think that could apply here:
Can you try with disabled "Check for publisher's certificate revocation" like...
(Found either via Internet Explorer* or Control Panel)
Our plug-ins are signed and there's a validity check taking place each time they're loaded. Sometimes this check can add additional latency. In your case it might be the debugging extensions causing the delay.
Please only try this workaround temporarily as it might be a security violation for you!
If this does not help can you please provide me more information, like:
- which product version are you using and for which architecture(s) (I assume it's 11.1 update 4 for 64 bit?)
- the underlying OS and Visual Studio version
- did you try to start a debugging session with all windows (BPs, threads, callstack, ...) closed; do you notice a difference?
I hope that helps you,
Georg Zitzlsberger
there can be various reasons why it (suddenly?) takes longer to start a debugging session. Let's start with something I think that could apply here:
Can you try with disabled "Check for publisher's certificate revocation" like...
(Found either via Internet Explorer* or Control Panel)
Our plug-ins are signed and there's a validity check taking place each time they're loaded. Sometimes this check can add additional latency. In your case it might be the debugging extensions causing the delay.
Please only try this workaround temporarily as it might be a security violation for you!
If this does not help can you please provide me more information, like:
- which product version are you using and for which architecture(s) (I assume it's 11.1 update 4 for 64 bit?)
- the underlying OS and Visual Studio version
- did you try to start a debugging session with all windows (BPs, threads, callstack, ...) closed; do you notice a difference?
I hope that helps you,
Georg Zitzlsberger
Thank you for providing more information.
There can be lots of other reasons for the long delay. I'd like to narrow it down with you by trying the following steps:
i) Please create a simple C/C++ "hello world" project (using VS compiler). Set a BP @ main and start the debugger. If there's the same latency the root cause is related to global configuration/environment.
ii) If not, try a simple Fortran "hello world" project (using IFORT) instead. Again, start the debugger. In case latency is experienced now, it's related to Fortran extensions, high likely because of the plug-ins.
iii) And last, if the steps above did not reproduce the problem, it must be related to your project.
Solutions:
If there's latency for case i), please check VS configuration. Maybe external symbols files are retrieved, e.g. via HTTP or network share.
(You'll find this configuration via "Tools->Options...;Debugging/Symbols")
Deactivate it or use caching instead.
In case there's latency for ii), you can temporarily deactivate our Fortran expression evaluation (FEE) plug-in by renaming ForDbgSW.dll (\Common7\Packages\Debugger\ForDbgSW.dll) to DONTUSE_ForDbgSW.dll. Please do that only with VS closed. Afterwards, start VS again and try to debug. I'd assume the latency is gone for this case now. Close VS again and rename the DLL back.
FEE is used for evaluations/watches/autos/... for all Fortran applications. Maybe there are windows open that make use of it (Autos, Locals, Watches, BPs, ...). Let me know if the problem still exists with just the source window open when starting & running the debugger.
If latency exists only for case iii):
Are there any dependencies on network shares? VS does not work well if projects or other components are stored non-local.
Please let me know about the result.
Best regards,
Georg Zitzlsberger
There can be lots of other reasons for the long delay. I'd like to narrow it down with you by trying the following steps:
i) Please create a simple C/C++ "hello world" project (using VS compiler). Set a BP @ main and start the debugger. If there's the same latency the root cause is related to global configuration/environment.
ii) If not, try a simple Fortran "hello world" project (using IFORT) instead. Again, start the debugger. In case latency is experienced now, it's related to Fortran extensions, high likely because of the plug-ins.
iii) And last, if the steps above did not reproduce the problem, it must be related to your project.
Solutions:
If there's latency for case i), please check VS configuration. Maybe external symbols files are retrieved, e.g. via HTTP or network share.
(You'll find this configuration via "Tools->Options...;Debugging/Symbols")
Deactivate it or use caching instead.
In case there's latency for ii), you can temporarily deactivate our Fortran expression evaluation (FEE) plug-in by renaming ForDbgSW.dll (
FEE is used for evaluations/watches/autos/... for all Fortran applications. Maybe there are windows open that make use of it (Autos, Locals, Watches, BPs, ...). Let me know if the problem still exists with just the source window open when starting & running the debugger.
If latency exists only for case iii):
Are there any dependencies on network shares? VS does not work well if projects or other components are stored non-local.
Please let me know about the result.
Best regards,
Georg Zitzlsberger
