debug
Get flash to fully experience Pearltrees
This article describes the limitations of Transact-SQL Debugger in SQL Server 2000. This article also provides guidelines and directions to troubleshoot basic problems related to Transact-SQL Debugger. However, this is not an exhaustive list, and some problems may be specific to your environment. 296539 (http://support.microsoft.com/kb/296539/EN-US/ ) BUG: T-SQL Debugger Doesn't Allow Stepping Through Stored Procedures with Same Name Owned by Non-DBO Users 328151 (http://support.microsoft.com/kb/328151/EN-US/ ) INF: T-SQL Debugger Is Turned Off By Default for Earlier Clients After You Install SQL Server 2000 Service Pack 3
INF: Transact-SQL Debugger Limitations and Troubleshooting Tips for SQL Server 2000
DBG 2.15.5 dbg-cli sources [325Kb] - May 1, 2007 gzip'd tar archieve includes dbg-cli sources for the client part (suitable for unix/linux platforms only).
DBG: Php Debugger: Downloads
Don’t run production ASP.NET Applications with debug=”true” enabled
One of the things you want to avoid when deploying an ASP.NET application into production is to accidentally (or deliberately) leave the switch on within the application’s web.config file. This last point is particularly important, since it means that all client-javascript libraries and static images that are deployed via WebResources.axd will be continually downloaded by clients on each page view request and not cached locally within the browser. This can slow down the user experience quite a bit for things like Atlas, controls like TreeView/Menu/Validators, and any other third-party control or custom code that deploys client resources. Note that the reason why these resources are not cached when debug is set to true is so that developers don’t have to continually flush their browser cache and restart it every-time they make a change to a resource handler (our assumption is that when you have debug=true set you are in active development on your site).