Using the Windows Debugging tool WinDBG you can attach a live process and debug. You can set up break-points at different function calls and debug when the process hits and stops to the break-points. When you do not have the source code (which is true for most of the products that we use as end user or support) this technique can be very useful. Today I will show you guys how to attach a UDL file to WinDBG to see your call flow under the hood. You can apply the same technique to attach your client application that is connecting to a database and having a connectivity issue.
Getting prepared
If you do not have WinDBG installed already then you can download the tool from the web WinDbg (32-bit) WinDbg (64-bit). There are three versions of the debugger package: 32-bit, x64 bit and ia64-bit. To select the right version, see Choosing a 32-bit or 64-bit Debugger Package.
Then you need the symbols. You can download the symbols or you can use Microsoft Symbol server. The following KB has the detailed steps to use the Microsoft Symbol server.
Use the Microsoft Symbol Server to obtain debug symbol files
http://support.microsoft.com/kb/311503Attaching a UDL file process to WinDBG
We will attach a Universal Data Link (.udl) file with the WinDBG and debug the process as we try to make a connection to a SQL Server. UDL files are most commonly used to trouble shoot connectivity issues. If you are not familiar with ULD file then please review the following link and create a test.udl file on your desktop.
Read more:
Data Access Technologies Posted via email from .NET Info
Posts
0 comments:
Post a Comment