Abstract: Systems, methods and computer program products are described that enable a diagnostic tool, such as a debugger, to evaluate an expression based on the state of a target program process where the expression to be evaluated includes a call to a first function that exists in the target program process but where evaluation of such first function requires evaluation of a second function that does not exist in the target program process. For an expression such as this, the diagnostic tool emulates execution of the first function within a process other than the target program process, such as within the diagnostic tool process. In other embodiments, the emulation capability of the diagnostic tool is leveraged to enable a user thereof to simulate a modification of the target program process without making actual changes to the target program process.

Abstract: Systems, methods and computer program products are described that enable a diagnostic tool, such as a debugger, to evaluate an expression based on the state of a target program process where the expression to be evaluated includes a call to a first function that exists in the target program process but where evaluation of such first function requires evaluation of a second function that does not exist in the target program process. For an expression such as this, the diagnostic tool emulates execution of the first function within a process other than the target program process, such as within the diagnostic tool process. In other embodiments, the emulation capability of the diagnostic tool is leveraged to enable a user thereof to simulate a modification of the target program process without making actual changes to the target program process.

Abstract: Threads operating in a computing environment often invoke service functions, such as methods of a programming library. Such invocations may sometimes cause a blocking of the thread, which may be protracted. A long pendency of the service function invocation and blocking of the thread may be acceptable in some operating contexts, such as the ordinary processing of the thread, but may be unacceptable in other operating contexts, such as while performing a function evaluation during debugging. Such blocking may be mitigated by redirecting a service function to an abort function if the service function is capable of blocking the thread and the thread is operating in a safe mode. The thread may then be permitted to execute, and the potentially blocking service functions may be avoided, resulting in a function evaluation abort (e.g., an exception) rather than a blocked thread and a failed debugging scenario.

Abstract: Threads operating in a computing environment often invoke service functions, such as methods of a programming library. Such invocations may sometimes cause a blocking of the thread, which may be protracted. A long pendency of the service function invocation and blocking of the thread may be acceptable in some operating contexts, such as the ordinary processing of the thread, but may be unacceptable in other operating contexts, such as while performing a function evaluation during debugging. Such blocking may be mitigated by redirecting a service function to an abort function if the service function is capable of blocking the thread and the thread is operating in a safe mode. The thread may then be permitted to execute, and the potentially blocking service functions may be avoided, resulting in a function evaluation abort (e.g., an exception) rather than a blocked thread and a failed debugging scenario.

Abstract: A software architecture for debugging the execution of T-SQL and managed data-tier application logic associated with a single connection, in isolation from other connections, is provided. In the architecture, a database server hosts the data-tier application logic. A client connects to the database server and issues requests on the connection, which initiates the execution of the data-tier application logic. A debugger debugs a client process on the server. An application program interface (API) receives a request to initiate a debugging session from the debugger, and returns an interface pointer to the debugger, thereby enabling the debugger to debug the client connection to the server.

Abstract: A software architecture for debugging the execution of T-SQL and managed data-tier application logic associated with a single connection, in isolation from other connections, is provided. In the architecture, a database server hosts the data-tier application logic. A client connects to the database server and issues requests on the connection, which initiates the execution of the data-tier application logic. A debugger debugs a client process on the server. An application program interface (API) receives a request to initiate a debugging session from the debugger, and returns an interface pointer to the debugger, thereby enabling the debugger to debug the client connection to the server.

Abstract: A minimally intrusive debugging system for use by multiple users for concurrently and independently debugging a common software target in a client and server debugging environment. The target software is a non-compiled interpreted script-type program that is individually controlled by independent client debugging sessions. Each debug engine in the client's debugging session is used to control the target software program using debug system library interface calls that are integrated into the executing target software program. The debug system library interface calls facilitate communication of target system program events to the client's debug engine and to extract internal operational information from said target software program by the client debug engine and target software program interface on each client computing device.

Abstract: A minimally intrusive debugging system for use by multiple users for concurrently and independently debugging a common software target in a client and server debugging environment. The target software is a non-compiled interpreted script-type program that is individually controlled by independent client debugging sessions. Each debug engine in the client's debugging session is used to control the target software program using debug system library interface calls that are integrated into the executing target software program. The debug system library interface calls facilitate communication of target system program events to the client's debug engine and to extract internal operational information from said target software program by the client debug engine and target software program interface on each client computing device.